Rails API backend preconfigured

To goal of this project is to have a production-ready deploy of an Rails 4 API backend in a few minutes.

It is a blank Rails app, preconfigured with:

Deployment stack is the following:

  • Rails 4.1;
  • Capistrano 3;
  • nginx configured via Capistrano task;
  • Puma configured via Capistrano task;
  • crontab with whenever;
  • asynchronous jobs with delayed-job;
  • auto backups for PostgreSQL;
  • environment variables with figaro;
  • error notification with airbrake;
  • both production and staging environments configured for Capistrano/nginx/puma;
  • configurable exception notification via email (exception_notification).

See wiki article on how setup the server accordinly (TODO).

Getting started

  • rename project name module
  • nome git
  • nome database
  • update application.yml da application.example.yml
  • nome app su deploy
  • indirizzo server

rake db:migrate

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Added some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request

    TMP

Deploy ultima versione del branch develop in ambiente staging cap staging deploy

Deploy revision a56ffeaed78a80a6d3afebfeaee1c1e4da3775b9 in ambiente staging REVISION=f37d74ab7ec1fba90e21444299000128e7783a86 cap staging deploy

È possibile anche pubblicare feature branch a patto non siano branch locali (git-flow publish) REVISION=feature/ZAT-557-capistrano-setup cap staging deploy

Deploy ultima versione del branch master in ambiente produzione: REVISION=master cap production deploy

N.B.Per produzione meglio fare una release con git flow

Comandi extra Restart cap deploy:restart

Restart nginx cap nginx:restart cap nginx:reload

Lista task Capistrano cap -vT

Logs: cd ~/apps/hfarm_user_admin_production/current/log/

Console: cd ~/apps/hfarm_user_admin_production/current RAILS_ENV=production bundle exec rails c

MONIT nginx