From 0b7d07f0a3996c9473de858f1cbcafa8bf2e3deb Mon Sep 17 00:00:00 2001 From: Louise Crow Date: Thu, 26 Mar 2015 11:16:00 +0000 Subject: Remove rails_app_server and rails_app_port They're not used in deploy.yml - the issue of different app servers is handled by using the service to restart the app. Fixes #2180. --- docs/installing/deploy.md | 9 +-------- 1 file changed, 1 insertion(+), 8 deletions(-) (limited to 'docs/installing/deploy.md') diff --git a/docs/installing/deploy.md b/docs/installing/deploy.md index 355c4f8a2..99b575efa 100644 --- a/docs/installing/deploy.md +++ b/docs/installing/deploy.md @@ -91,14 +91,7 @@ Next, on your local machine: `config/deploy.yml` appropriately -- for example, edit the name of the server. Also, change `deploy_to` to be the path where Alaveteli is currently installed on the server -- if you used the installation - script , this will be `/var/www/[HOST or alaveteli]/alaveteli`. If - you're running the thin application server rather than passenger (you - will be if you installed using the install script), - you'll need to set `rails_app_server` to `thin` and `rails_app_port` - to whatever port it's running on. If you installed with the install - script, this will be port 3300. - - + script , this will be `/var/www/[HOST or alaveteli]/alaveteli`. * `cd` into the Alaveteli repo you checked out (otherwise the `cap` commands you're about to execute won't work) * still on your local machine, run `cap -S stage=staging deploy:setup` to setup capistrano on the server -- cgit v1.2.3