Install Self-Hosted
Get Started on Cloud
BasicsPipelinesActions & ServicesIntegrationsSelf-HostedYAMLBuddy GitTroubleshootingAPI

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.

Image loading...Example pipeline with deployment to Rackspace

Tip
If you are new to Buddy, check out our workflow guides that will tell you how to build, test and deploy your type of application.
Hint

📚 Learn more about Rackspace action features, integrations and alternatives.

Configure pipeline in Buddy

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

Image loading...Creating new project

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

Image loading...Adding new pipeline

Configure Rackspace Container

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

Image loading...Creating container in Rackspace

  1. 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)

Image loading...Container details in Rackspace

Configure Rackspace deployment

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

Image loading...Adding Rackspace action

Hint
Read how to configure Rackspace with YAML.
  1. 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
Warning
If you are using build actions in your pipeline, make sure to select the Filesystem as the source to deploy artifacts and processed files.
  1. In the Path field, specify whether to deploy the entire filesystem content or a specific folder e.g. /build directory:

Image loading...Transfer tab in Rackspace action configuration window

Hint
The 'Delete files removed in changeset' flag lets you decide whether to delete the files when they are deleted during the deployment. If not selected, the added files will be kept all the time.
Tip
The 'Ignore files using paths and patterns' section lets you exclude certain extensions, files and folders.
  1. In the Target tab:

Image loading...Target tab in Rackspace action configuration window

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

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

Hint
Buddy's deployment is based on changesets. This means only changed files are deployed, which makes it lightning fast ⚡️. The first deployment is always performed from scratch, unless you set a revision on the server in the Options tab.
  1. When ready, click Add this action to finish configuration.
Success
Congratulations! Your pipeline is ready for Rackspace deployments 🥳

Last modified on Sep 24, 2024

Previous pageNetlifyNext pageRsync