Deploy to Rackspace

How to deploy to Rackspace?

Deploying to Rackspace with Buddy involves setting up a pipeline that allows you to automatically update your Rackspace Cloud Files on every push to branch. You can also run your pipeline manually or schedule recurrent deployments.

Example pipeline with deployment to Rackspace

Configure pipeline in Buddy

1. Create a new project in Buddy and select your Git provider.

Creating new project

2. Add a new pipeline and configure the details: name, trigger mode, and a branch from which you want to deploy.

Adding new pipeline

Configure Rackspace Container

1. Make sure to define the container in your Rackspace account under Storage → Files:

Creating container in Rackspace

2. Click Create Containers and specify container details:

• name
• region (here's a list of available Rackspace regions to choose from)
• type - whether the created container should be private, public, or a static website (in our case, the container should be Private as files copy will be kept in it)

Container details in Rackspace

Configure Rackspace deployment

1. Look up and click Rackspace on the action list to add it to the pipeline:

Adding Rackspace action

2. The action has five configuration tabs:

• Transfer – here you define the source path, deployment flags, and files to ignore
• Target – here you select the Rackspace integration, region, container, and path
• Variables – here you can add and modify environment variables required by your workflow
• Conditions – here you configure the trigger conditions for which the action will run
• Options – here you define the action's name and behavior on failure and timeout

3. In the Path field, specify whether to deploy the entire filesystem content or a specific folder e.g. /build directory:

Transfer tab in Rackspace action configuration window

4. In the Target tab:

• select an existing or add a new Rackspace integration
• choose a region in which the container was created.

Target tab in Rackspace action configuration window

5. If both fields are selected correctly, you should be able to see the created container on the containers list.

6. Finally, select the target path where the files will be deployed and test the connection to see if the action works correctly.

7. When ready, click Add this action to finish configuration.