Deploy WordPress packages by using Rackspace Cloud Orchestration
Rackspace Cloud Orchestration for Cloud Servers simplifies the process of creating a WordPress environment, either as a stand-alone server or in a multiple-server cluster. This article shows how to deploy WordPress packages by using Cloud Orchestration.
Deploy the servers
Log in to the Cloud Control Panel.
In the top navigation bar, click Orchestration, and under Create Resources, click Stack.
Specify a name and region for your stack.
In the Application Name list, select WordPress and then choose the flavor, either Single Linux server or Multiple Linux servers.
Click Next Step.
On the next page, specify server and WordPress settings.
Under Advanced Options, enter the database name.
Click Create Stack.
On the stack details page you will see a green Up status in the status field when the stack is complete.
Access the servers
After your stack is active, go to the Stack Details page and click View Credentials to access the login information for your new servers.
In the Stack Credentials window, you will see an SSH private key that you can use to access the servers in your stack as the root user, the root password for the database, and the WordPress password.
For more information about using the provided SSH key to access your servers, see Logging in with a SSH private key on Windows or Logging in with a SSH private key on Linux and Mac.
Set up DNS
If you host your DNS with Rackspace DNS, you can now add a DNS record for your new WordPress stack. For information about adding a DNS record, see Creating DNS Records for Cloud Servers. Point your domain to the public IP address of the load balancer that was created for you.
If you are not ready to use public DNS with WordPress, modify your desktop’s Hosts file to point your domain to your new stack. For information about modifying your Hosts file, see Modify your hosts file. Be sure to use the load balancer public IP address.
After you are finished, you can start using WordPress by navigating to the URL that you entered during the stack configuration.
Continue the conversation in the Rackspace Community.
©2016 Rackspace US, Inc.
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License