diff options
| author | azul <azul@riseup.net> | 2013-03-14 07:36:54 -0700 |
|---|---|---|
| committer | azul <azul@riseup.net> | 2013-03-14 07:36:54 -0700 |
| commit | 869ba2f363a48d0f76321efc08a228f54aeb6758 (patch) | |
| tree | 00944b79cd5abb5058ac2ea432c32ea433b1aebd /DEPLOY.md | |
| parent | 886585a0f673e0ea70abb99504ff9c70180361d5 (diff) | |
| parent | 1f874dc62e0d0add285f6ab5ff1b6d8fccaa1912 (diff) | |
Merge pull request #37 from azul/feature/migration-flow
Migration flow for couch db
Diffstat (limited to 'DEPLOY.md')
| -rw-r--r-- | DEPLOY.md | 19 |
1 files changed, 16 insertions, 3 deletions
@@ -9,8 +9,8 @@ These instructions are targeting a Debian GNU/Linux system. You might need to ch The following packages need to be installed: * git -* ruby1.8 -* rubygems1.8 +* ruby1.9 +* rubygems1.9 * couchdb (if you want to use a local couch) ### Setup Capistrano ### @@ -25,5 +25,18 @@ run `cap deploy` to deploy to the server. Please make sure your deploy includes the following files: -* config/cert * public/config/provider.json +* config/couchdb.yml + +## Couch Security ## + +We recommend against using an admin user for running the webapp. To avoid this couch design documents need to be created ahead of time and the auto update mechanism needs to be disabled. +Take a look at test/setup_couch.sh for an example of securing the couch. After securing the couch migrations need to be run with admin permissions. The before_script block in .travis.yml illustrates how to do this: + +``` +mv test/config/couchdb.yml.admin config/couchdb.yml # use admin privileges +bundle exec rake couchrest:migrate_with_proxies # run the migrations +bundle exec rake couchrest:migrate_with_proxies # looks like this needs to run twice +mv test/config/couchdb.yml.user config/couchdb.yml # drop admin privileges +``` + |