Hold on to your hats, because this post is going to extend my personal “geek quotient” a bit and may for you as well. As you read, keep in mind I’m a teacher and school technology director, not a full time coder or web developer. I’m sharing this post to document my own learning curve today for future reference, and in case this information and these links are helpful to others.

I currently pay the web hosting company Site5.com a hefty chunk of monthly change to host about 35 different WordPress websites. I use and update a few of these regularly, but most of them are either for non-profits or are for sites I rarely change and few people access. I pay for a VPS (virtual private server) which gives me a fixed amount of storage space and bandwidth per month. I manage and update these websites primarily using cPanel, which is a graphical user interface provided by many website hosts so customers don’t have to use command line / console / terminal commands to make changes to their remote files and websites. I’ve used some multi-site management tools in the past for keeping my sites updated and patched, but don’t currently use any. This can be a pain and can get time consuming.

Last week I visited with Ben Wilkoff (@bhwilkoff) about different WordPress hosting options, and he told me about the Google Cloud Platform. Like Amazon’s Cloud Services, Google has built a scalable and affordable option for web as well as application developers to host different kinds of content online. I have hosted all my podcasts (probably around 700 episodes) on Amazon S3 for several years, and that has proven to be an extremely cost-effective option rather than saving those files on my main web hosting account. For more background about this, see my January 2014 post, “Why I Switched My WordPress Web Host from WP Engine to Site5.

My wife and I made some plans last week when we were camping on vacation which involve a new WordPress website, so today I thought I’d give the Google Cloud Platform a try. Rather than use these WordPress installation instructions, which involve some command line configurations, Ben directed me to the web service Bitnami and these instructions for using “Bitnami Launchpad for Google Cloud Platform.”

I followed those instructions and was able to register with the Google Cloud Platform, register with Bitnami, and install WordPress on a dynamic / ethereal IP address. That’s the default IP address which is initially used with this setup. It works fine, but the IP address of your actual site changes each time the server is restarted. This isn’t a problem for test sites, but definitely isn’t the configuration you want for a site that will be in “production” or in use publicly by others.

Earlier in the day I registered the domain I want to use for this new project using a separate domain name registrar. After I had my new WordPress installation setup, I used these instructions to request/configure a static IP address with Google Cloud Services for my WordPress installation instance. I was then able to login to my domain name registrar and “point” my domain to that IP address by changing the “A Record.”

Google provides a 60 day trial with $300 of “free virtual money” to use on any web application or site you want to configure on their Google Cloud Platform. After that period, fees apply and you’ll pay for the virtual resources which are consumed/utilized for your projects. I setup my WordPress site today as a “micro-site,” so the estimated costs are about $4.43 per month. That is MUCH less than I’d pay if I was setting this up on a new, bottom tier account with a traditional web hosting company.

I’m not completely sure I’m going to leave this new website on this Google Cloud Platform / Bitnami installation setup, but I’m going to give it a try for at least 60 days. If I need to migrate the website over to my current web host / VPS account, I’ll probably use the free WordPress plugin “All-in-One WP Migration” to do that.

Have you had positive or negative experiences hosting WordPress websites on Google Cloud Platform via Bitnami or another service/host? Depending on your situation and “geek quotient” this may be a good option to consider, from a cost as well as performance standpoint.

Many thanks to Ben Wilkoff for pointing me toward Google Cloud Platform and Bitnami. If you don’t follow him yet on Twitter (@bhwilkoff) you should! Also check out his amazing video presentation for the 2014 K-12 Online Conference: “6 Second Stories for Learning.” Ben is not only wicked-smart when it comes to educational technology, he’s also one of the kindest people you’ll ever meet!

Thank you Ben Wilkoff!

If you enjoyed this post and found it useful, subscribe to Wes' free newsletter. Check out Wes' video tutorial library, "Playing with Media." Information about more ways to learn with Dr. Wesley Fryer are available on wesfryer.com/after.

On this day..

Tagged with →  
Share →

4 Responses to Experimenting with WordPress on the Google Cloud with Bitnami

  1. Hasan Raza says:

    I launched my WordPress site on google cloud using 7 simple steps:

    Step 1: Sign up for free on cloudways.com.
    Step 2: Select Google Compute Engine server which is also available now on a 3 day trial period.
    Step 3: Select WordPress CMS according to your requirement from WordPress, Multisite, or WooCommerce.
    Step 4: Select Server Size according to your requirements
    Step 5: Select server Location according to your nearest audience
    Step 6: Select network bandwidth.
    Step 7: Select storage size and launch.

    For complete information visit: https://www.cloudways.com/blog/wordpress-on-google-cloud/

  2. Dominic Robillard says:

    Great article. Are you still hosting you WP using the Google Cloud Platform?

  3. Craig_Hubley says:

    We recently had a disturbing experience where AWS modified an image that had been created by Bitnami Cloud Hosting and was currently managed by it. It just “stopped” from BCH’s perspective, and had to be manually restarted. One could login to it with the old .pem and .ppk files, but, SQL access & PHP didn’t work because of errors:

    “”PHP: syntax error, unexpected $end, expecting ‘]’ in /opt/bitnami/php/etc/php.ini on line 1
    DB connection error: No such file or directory (localhost:3306)”
    – this was on Ubuntu and the DB connection was to MySQL

    this message suggests to me that basic aspects of PHP & database connectivity had just become destroyed by whatever AWS did to the image. It broke not only mediawiki but it’s dumpBackup.php script therefore making it impossible to back up that wiki.

    There was really no resort but to back up to a nine day older backup, losing files that had since been updated in the wiki, which should never *NEVER* happen & in a large organization would be beyond unacceptable and would end AWS use.

    AWS should have flagged this as a BCH-created and BCH-managed image and not touched it, regardless of the request (which came from the ignorant client to resize it).

    What I’m wondering is, does hosting BCH images on Google Cloud have the same or worse problems? BCH claims they can drop an image to your own management directly on AWS (or Google Cloud) any time, but if they don’t do this *BEFORE* a resizing or other modification, does that cause such chaos usually?

  4. Craig_Hubley says:

    Would you recommend this configuration for WooCommerce? If not, why not?

Creative Commons License
This work is licensed under a Creative Commons Attribution 3.0 Unported License.

Sharing from Matthews, North Carolina! Connect with Wes on Mastodon.