Skip to content
This repository has been archived by the owner on Jan 30, 2018. It is now read-only.

Updating Teambox

dz0ny edited this page Aug 9, 2010 · 11 revisions

Before updating your Teambox installation, it’s good practice to backup your database. If you’ve already done that, read below for instructions for Linux or Heroku.

What we will do is, basically:

- Use Git to save your configuration changes to a safe place.
- Pull the new Teambox code.
- It’s possible that you’ll need to do a Git merge on this point. If you find this problem, refer to our mailing list
- Restore your configuration changes.
- Migrate the database.
- Restart the server.

It’s important to have some basic knowledge of Git before performing this. It is possible that you will find yourself having to perform a Git merge if we introduce new settings to configuration files.

Installed locally (Linux: Ubuntu, Centos,…)

git stash # this saves your changes to files in a stash
git pull  # this gets the new teambox code
bundle install # this updates the gems
git stash pop # now we can restore your configuration changes
rake db:migrate RAILS_ENV=production
rm public/sprockets.js # cached version of JavaScript libraries, will auto-generate itself automaticaly  

At this point, you can restart the server. For Passenger, this is done with:

touch tmp/restart

Discussion

Installed on Heroku

git stash 
git pull origin master
git stash pop
git push heroku master
heroku rake db:migrate

Heroku will restart automatically. If it doesn’t, just do “heroku restart”.

Discussion

Clone this wiki locally