How to Deploy WordPress to the Cloud

By February 8, 2013 HowTo 15 Comments
Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedInEmail this to someone

wordpress-logo-stacked-rgbI think almost all people connected in one or another way with web know what WordPress is, but let’s examine in short this great PHP CMS and its main benefits.

WordPress is web software you can use to create a beautiful website or blog and it’s absolutely free. It is the platform of choice for over 60 million people and high profile establishments such as the American Government, the CIA, the FBI, the Airforce and many more. We also have chosen WordPress for our blog.

Here are few reasons of why WP is so popular:

  • It’s very easy to use and has an intuitive interface.
  • You have full control of nearly every aspect of your site.
  • You can extend the functionality of your site with different plugins.
  • WordPress sites are very scalable.
  • You can set-up multiple users for the website and assign access levels and capabilities to each user.
  • You can login from any Internet connected computer and manage your site.
  • WordPress is a self-contained system and does not require HTML editing software.
  • It’s easy to backup your website.
  • it’s SEO friendly and much more.

Such a great application needs a great hosting. So, let’s deploy WordPress application to Jelastic cloud right now!

Create an environment

1. Go to Jelastic.com and sign up if you haven’t done it yet or log in with your Jelastic credentials by clicking the Sign In link on the page.

2. While in Jelastic dashboard, click the Create environment button:

12

3. In the Environment Topology window pick Apache application server , the database you want to use (MySQL or MariaDB) and choose PHP v5.3. Then type your environment name, for example, wordpress.

1

In a minute your environment with both Apache and MySQL will be created and appears in the environments list.

Upload the application

1. Go to official web-site and download .zip archive by clicking Download WordPress 3.5.
2

2. Upload this .zip archive to the Deployment manager.

3

3. Once the package is in Jelastic, deploy it to the environment you have just created.

4

Configure database

1. Once the deployment is finished, click Open in browser button for MySQL

2. When you created the environment, Jelastic sent you an email with credentials to the database. Create an account and the database with the application using these credentials.

5

6

Install WordPress

1. Click the Open in browser button for Apache in your environment.

7

The WordPress installation will be started.

2. If the following message appears just click Create a Configuration File button.

8

3. Then click Let’s go!

9

4. In the opened window fill in fields in the following way:

  • Database name > type database name that was created on the step of configuring database.
  • Database username > type username (root by default).
  • Database password > type password (which you got by email).
  • Database host > insert link of your database (without “http:// ” and “/”).

10
Then click Submit.

5. Now run the process of installing WordPress by clicking Run the install button

11

6. Fill the last form and you will have your own WordPress in Jelastic PHP Cloud.

14

7. Log in with the credentials you have specified during the installation.

16

Enjoy!

17

WordPress has become an industry standard and is one of the top choices for blogging and CMS websites. It’s absolutely rocks for providing an easily accessible publishing platform, for both content producers and content consumers and now you can easily have it up and running in the cloud.

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedInEmail this to someone

15 Comments

  • Arthur R says:

    Please explain how to best to deploy a larger number ( multiple ) of WordPress websites using Jelastic. Each WordPress domainname website should have its own separate (domain name) database and a separated ‘virtualized (?) environment’. Ideally the set up should include a central admin/control hosting panel ( a Jelastic or third party one) easily enabling the use and updating of WP plug-ins (+updates) and (individual) themes for the respective WordPress sites. Using ‘WordPress Multisites’ (one database) resulted in many problems with non functional themes and plug-ins.

    • You can create one environment, deploy WP in there and then just simply clone it (by clicking the Clone button) as many times as you need.

    • Arthur R says:

      Thank you Marina for your (partial) reply. But does Jelastic also include a central admin panel to maintain all these ‘cloned’ WordPress websites making central updating (and managing) of all installed plug-ins and themes of these WP sites possible. Or do each of these through ‘cloning’ created ‘Jelastic Word Environments’ (= a domain name WordPressite ?) need to be individually maintained through the WordPress Admin panel of that website ? Does each Jelastic environment then have its own Apache and MySQL etc as a self ‘contained environment’ ? How much (unnecessary due to duplication ?) demand will having many separate Jelastic environments place on server and IT resources etc. for let’s say hosting 20 WordPress domainwebsites ? Looking into this problem I so far found only one dedicated WordPress hosting company with an overall centralized admin panel for all (separated!) WordPress domainname websites. Using the Standard WordPress Multisite set up resulted in a complete mess! I would expect many others are looking for manageable set up for easily hosting say 20 WordPress websites ? With Drupal it is all pretty straightforward. The following article gives an overview of various solutions, but what of that can be made and set up to work with Jelastic is the golden question we would much appreciate your expert advice on not being seasoned system administrators / programmers nor knowledgeable about Jelastic .. Or are we ‘condemned’ to a WordPress only hosting company ? Article: http://wpmu.org/maintain-all-your-wordpress-websites-from-a-central-location/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+Wpmu-Wordpress-Mu-PluginsThemesAndNews+%28WPMU.org+-+WordPress+MU+plugins%2C+themes+and+news%29

      • Thanks for interesting question! Unfortunately, we don’t provide any special admin panels for managing WordPress sites. In this case you can work with each of your sites separately and with separate Apache and MySQL for each site. Jelastic is not SaaS solution, it is hosting platform.

  • Great post, I liked it!

    Can we upload themes and/or plugins just using the wordpress admin panel with this setup? Are there any restrictions for file access, I mean, are the permissions set up?

  • Thanks for the quick response. Jelastic will be my #1 choice when I decide to go off WordPress hosting.

  • Arthur R says:

    Could explain more on the ‘cloning’ functionalities and advantages of Jelastic from a WordPress sitedeveloper / webhoster perspective? This to get a clearer understanding and follow best practices.
    1. Exactly what is ‘cloned’ through the Clone Button in the case of e.g. a WordPress site with core WordPress code plus various plug-ins a few theme(s), website content and a MSQL database for the site?
    2. How could the ‘Cloning’ functionality be used in initial stages of WP website development when testing out various plug-ins, themes etc? Can an ‘automatic’ or ‘manual’ website (plus database) backup system be set up during the site development process to easily return to an earlier ‘version’ of the website, plugins etc plus database prior to your latest changes (e.g. installation of WordPress plug-in or plug-in update or theme change?). If not with Jelastic how could a multiple series of site (environment?) backups be achieved to have an easy and efficient ‘development’ environment ?
    3. Trying to envisage how to have an initial site development environment, a production site hosting environment and subsequent environment for testing changes to the ‘production site’ could you share your best practices experiences with us ?

    • Arthur R says:

      http://jelastic.com/docs/clone-environment

      This weblink gives some more information on the Jelastic ‘clone-environment’

    • Hello, Arthur!
      Sorry for the delay with answer!

      >Exactly what is ‘cloned’ through the Clone Button in the case of e.g. a WordPress site with core WordPress code plus various plug-ins a few theme(s), website content and a MSQL database for the site?

      After cloning the environment you will get the exact copy of your current environment with all code, plugins etc.

      >2. How could the ‘Cloning’ functionality be used in initial stages of WP website development when testing out various plug-ins, themes etc? Can an ‘automatic’ or ‘manual’ website (plus database) backup system be set up during the site development process to easily return to an earlier ‘version’ of the website, plugins etc plus database prior to your latest changes (e.g. installation of WordPress plug-in or plug-in update or theme change?). If not with Jelastic how could a multiple series of site (environment?) backups be achieved to have an easy and efficient ‘development’ environment ?

      If you want to return an earlier version of your site, than you can easily swap domains between your early and current environments as it’s described here http://jelastic.com/docs/swap-domains

      >3. Trying to envisage how to have an initial site development environment, a production site hosting environment and subsequent environment for testing changes to the ‘production site’ could you share your best practices experiences with us ?

      As you have already mentioned, we have a detailed instruction published http://jelastic.com/docs/how-to-manage-the-application-lifecycle-in-jelastic

      >The above link deals with ‘application lifecycle management’ and does not seem to relate to how to best manage a ‘WordPress website lifecycle’ ….

      It’s just an example, it’s not related to WP, but you can use some of these practices for your needs.

      Hope you’ll find my answers useful:)

  • Fabio says:

    How can I configure wildcard subdomain?
    I have tried to configure apache httpd.conf file using vhosts and restarted apache server:

    ServerAdmin root@localhost
    DocumentRoot /var/www/webroot/ROOT
    ServerName myexempledomain.com
    ServerAlias *.myexempledomain.com
    ErrorLog logs/dummy-host.jelastic.com-error_log
    CustomLog logs/dummy-host.jelastic.com-access_log common

    But It did not work.
    Could you please help me?

Leave a Reply

Subscribe to get the latest updates