Posted over 1 year ago. Visible to the public.


New Deployments

Looking for a checklist for new deployments? You will find it here -> Adding new deployments


As you should already know from 100 Infrastructure basics we always have two independent servers running your application which is the reason your deployment process has to accommodate two deployment targets.

If you are a opscomplete customer you have your own servers so the server hostnames could look like this:



For the deployment and running of other services we create users on our servers for you. Depending on the circumstances they get named after your project or your companies name.
To give you an idea how that looks like:
If you have only one deployment we usually would name the user for the staging deployment deploy-acme_s and for production it would be deploy-acme_p.

We allow user logins via SSH Public Key Authentication ( only. Please use ssh-keygen to generate a keypair and send us the public key.

Good to know

Since you can log into your deployment server via SSH we also made it easier to reach your deployment directory by typing appdir.

Copy$ appdir$


Your application will live in /var/www/ on the application servers with a couple of other important directories. The directories you find in your deployment dirs are based on the Capistrano Directory Structure.
The following shows a freshly deployed directory structure:

root@server:/var/www/ tree -d -L 2 . ├── current -> /var/www/ ├── log ├── releases │   └── 19700101000000 └── shared ├── config │ ├── database.yml │ └── secrets.yml ├── log ├── pids ├── public │   └── system -> /gluster/shared/ ├── storage -> /gluster/shared/ └── system -> /gluster/shared/

The current directory is a symlink that always points to the last successful deployment done by capistrano. In 201 Capistrano Sample Receipe you can download a sample configuration which should help you get started with your deployment setup.

In the next directory releases there are previous deployments you can roll back to in case something goes wrong. You can read more about those directories here.

In the directory shared there are three more directories (config, storage and system) which we can put on glusterfs a filesystem that is shared between the application servers if this is something your application benefits from.

We also create a config/database.yml and config/secrets.yml for you.

The config/database.yml is managed by us and all changes will get overwritten.

The config/secrets.yml will get created for Ruby on Rails projects with a generated secret_key_base entry and is not managed by us. So you can change it to meet your needs.

Synced directories

Check carefully which directories are symlinks pointing to glusterfs (/gluster/shared/). Only these directories are shared among the servers.


If your application uses a database (MySQL or PostgreSQL, others upon request) we automatically deploy a database.yml which includes host and credentials to access it.

Optionally it is possible to have multiple Redis instances configured as well.


Requests get to your application via our load balancers. The default method we use is called IP hash which means a client accessing your application is always directed the same application server. This ensures - if for example your application has sessions that are not synchronized between application servers - that the user always hits the server his active session exists on.

If you are not limited by this constraint we can use a round robin method as well. Please contact us in this case or if you have questions regarding this topic!

Owner of this card:

Thomas Eisenbarth
Last edit:
5 months ago
by Claus-Theodor Riegg
Posted by Thomas Eisenbarth to opscomplete
This website uses cookies to improve usability and analyze traffic.
Accept or learn more