Deploying From Git¶
API Umbrella should be installed onto servers using the binary packages. However, if you want to deploy more recent updates from master (or your own forked changes), then newer versions of the app can be deployed on top of a package-based installation. Deployments are automated through Capistrano.
In order to run the deployment scripts, your local computer (or wherever you’re deploying from) must have:
- Ruby 1.9+
- Ruby Bundler
If you have trouble getting any of these setup locally, you can also run deployments from the development virtual machine, which includes these dependencies.
First-Time Server Setup¶
On each server you wish to deploy to, you must setup SSH keys so that you can deploy as the
api-umbrella-deploy user (this user is automatically created as part of the package installation). These steps only need to be performed once per server.
On Your Computer¶
- Ensure you have SSH keys: You must have SSH keys setup on your local computer (or wherever you’re deploying from). If you do not have SSH keys, see steps 1 & 2 from GitHub’s Generating SSH keys guide for instructions.
- Copy your public key: Copy the contents of your public key (often at
~/.ssh/id_rsa.pub). For more tips on copying, or alternative locations for your public key, see step 4 from GitHub’s Generating SSH keys guide.
On Each Server¶
With your public SSH key in hand from your own computer, follow these steps on each server, replacing
$ echo "YOUR_PUBLIC_KEY" | sudo tee --append /home/api-umbrella-deploy/.ssh/authorized_keys
Check out the api-umbrella repository from git:
$ git clone https://github.com/NREL/api-umbrella-router.git router
Install the deployment dependencies from inside the
$ cd api-umbrella/deploy $ bundle install
Define your destination servers: Add a
.envfile inside the
routerdirectory defining the servers to deploy to for the “staging” or “production” environments:
Servers can be defined using hostnames or IP address. Multiple servers can be comma-delimited. In this example there are two staging servers (
10.0.0.2), and two production servers (
Deploy to either the “staging” or “production” environments:
$ cd api-umbrella/deploy $ bundle exec cap staging deploy $ bundle exec cap production deploy