Foodsoft/foodsoft
1
1
Fork 0
Code Issues 36 Pull requests 5 Projects 1 Releases Wiki Activity

Remove Capistrano (#491, PR #521)

Browse source
This commit is contained in:
wvengen 2017-10-28 19:50:02 +02:00 • committed by GitHub
parent c35205c1b0
commit f5bea41ccf
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
10 changed files with 0 additions and 338 deletions
Download patch file Download diff file Expand all files Collapse all files

37
doc/DEPLOYMENT.md
View file

@ -58,40 +58,3 @@ In practice, you'd probably want to use docker-compose. If you know Docker well
you'll have no problem to set this up. For inspiration, look at the
[foodcoops.net production setup](https://github.com/foodcoops/foodcoops.net).
## Capistrano
### Setup
1. Initialise your [Capistrano](http://capistranorb.com/) setup
bundle exec cap install
sed -i 's|^# \(require.*rails.*\)|\1|' Capfile
cp config/deploy.rb.SAMPLE config/deploy.rb
When you're using [RVM](http://rvm.io/) on the server you may want to
uncomment the corresponding line in `Capfile`.
2. Adapt your configuration in `config/deploy.rb` and `config/deploy/*.rb`
### Deploy
On your first deploy you should run (choose either staging or production)
bundle exec cap staging deploy:check
This will fail, which is ok, because there is no configuration yet. On your
server, there is a directory `shared/config` for each installation, which
contains the configuration. Create `database.yml`, `app_config.yml` and
`initializers/secret_token.rb` and try again.
(See `lib/capistrano/tasks/deploy_initial.cap` for a way to automate this.)
Deploy to staging
bundle exec cap staging deploy
Deploy to production
bundle exec cap production deploy