Deployment guide

One easy way of deploying ASI is using Capistrano. The code has already a config/depoy.rb file that has few preconfigured servers. You can add your own to the if at the start and set all the variables according to your own server. Then the deployment should be as easy as:

  cap deploy DEPLOY_ENV=name_of_your_server

The cap command will read the local deploy.rb file and excecute the required actions by using ssh, so you'll need to have ssh access to the target server and set the user in deply.rb accordingly. The deploy basically retrieves the lates code from the repository. For any information that is server specific and should not be overwritten, the shared folder should be used. There are some symlinks made everytime a new deploy is run (e.g. to config.yml and database.yml) and it is possible to add more of those by modifying the deploy.rb. Generally, it is a good idea to gather most of the server specific settings to config.yml, but if there is need for other files in shared, they can be added.

More info about how Capistrano works can be found for example here The list of available Capistrano commands can be seen with command:

  cap -T