# on production servers its often a good idea not to store svn passwords.
# heres a one-liner to do just that:
echo "store-passwords=no" >> ~/.subversion/servers && rm -f ~/.subversion/auth/svn.simple/*

bash

1

svn ignore passwords

# on production servers its often a good idea not to store svn passwords.
# heres a one-liner to do just that:
echo "store-passwords=no" >> ~/.subversion/servers && rm -f ~/.subversion/auth/svn.simple/*

copy | embed

• bash, 
• development, 
• production, 
• svn

find . -name ".svn" -type d -exec rm -rf {} \;

bash

1

remove .svn folders

find . -name ".svn" -type d -exec rm -rf {} \;

copy | embed

• bash, 
• development, 
• production, 
• server, 
• svn

rake db:migrate RAILS_ENV=production

rb

1

Run DB Migrate on production

rake db:migrate RAILS_ENV=production

copy | embed

• db, 
• migrate, 
• production, 
• rails, 
• rake

# in the Warehouse settings page:
#  Shell command to run when permissions are updated:

rake warehouse:build_config REPO=:subdomain CONFIG=config/:subdomain.access

# Note 1:  the above works for both the :path URL method
#   (eg http://wh.example.com/reponame/)  
# as well as the :subdomain URL method 
#   (eg http://reponame.wh.example.com/)
#
# During WH setup, you should create a symlink to the .access file created 
# by the Dreamhost panel for each repo you want to control with Warehouse.

cd /your_web_app_directory/config
ln -s /home/username/svn/reponame.access

bash

1

Warehouse permission settings on Dreamhost

# in the Warehouse settings page:
#  Shell command to run when permissions are updated:

rake warehouse:build_config REPO=:subdomain CONFIG=config/:subdomain.access

# Note 1:  the above works for both the :path URL method
#   (eg http://wh.example.com/reponame/)  
# as well as the :subdomain URL method 
#   (eg http://reponame.wh.example.com/)
#
# During WH setup, you should create a symlink to the .access file created 
# by the Dreamhost panel for each repo you want to control with Warehouse.

cd /your_web_app_directory/config
ln -s /home/username/svn/reponame.access

copy | embed

• dreamhost, 
• production, 
• warehouse

# restart a Rails Web Application on DreamHost. this requires that you've 
# enabled mod_rails (Passenger) support for the app in the DreamHost panel

$ touch /your_web_app_directory/tmp/restart.txt

# Passenger looks for a file tmp/restart.txt and if it exists, it reloads 
# your app, and refreshes all your files then deletes the tmp/restart.txt file

# The other way to force a restart is through the dreamhost panel:
# Domains > Manage Domains > Edit your-app.domain.com 
#  >> submit the form through the "fully host this application" button.

bash

1

restart a Rails Web Application on DreamHost.

# restart a Rails Web Application on DreamHost. this requires that you've 
# enabled mod_rails (Passenger) support for the app in the DreamHost panel

$ touch /your_web_app_directory/tmp/restart.txt

# Passenger looks for a file tmp/restart.txt and if it exists, it reloads 
# your app, and refreshes all your files then deletes the tmp/restart.txt file

# The other way to force a restart is through the dreamhost panel:
# Domains > Manage Domains > Edit your-app.domain.com 
#  >> submit the form through the "fully host this application" button.

copy | embed

• dreamhost, 
• production, 
• rails