Difference between revisions of "Updating"

From diaspora* project wiki
Jump to: navigation, search
(Created page with "Updating Diaspora is fairly straight forward. But sometimes there are special procedures or updates, so always read the [https://github.com/diaspora/diaspora/blob/master/Chang...")
 
Line 1: Line 1:
 
Updating Diaspora is fairly straight forward. But sometimes there are special procedures or updates, so always read the [https://github.com/diaspora/diaspora/blob/master/Changelog.md changelog] first.
 
Updating Diaspora is fairly straight forward. But sometimes there are special procedures or updates, so always read the [https://github.com/diaspora/diaspora/blob/master/Changelog.md changelog] first.
  
== Updating a production install ==
+
= Updating a production install =
  
 
We need to update the code first:
 
We need to update the code first:
Line 31: Line 31:
 
Now you need to restart Diaspora. To do this with the standard startup method you need to get to the place where you run <tt>./script/server</tt>, hit <tt>Ctrl+C</tt> and run it again.
 
Now you need to restart Diaspora. To do this with the standard startup method you need to get to the place where you run <tt>./script/server</tt>, hit <tt>Ctrl+C</tt> and run it again.
  
== Updating a development install  ==
+
= Updating a development install  =
  
 
Just checkout the develop branch, pull (from upstream), rebundle and migrate the database:
 
Just checkout the develop branch, pull (from upstream), rebundle and migrate the database:

Revision as of 08:29, 22 June 2013

Updating Diaspora is fairly straight forward. But sometimes there are special procedures or updates, so always read the changelog first.

Updating a production install

We need to update the code first:

git pull

Read the output! If you made local modifications to files tracked in git, it might refuse the update or place conflict markers into the files which need to be resolved. If you run on PostgreSQL and get a message about Gemfile.lock try git checkout Gemfile.lock first.

Now we need to update the Ruby libraries:

bundle # Or DB=postgres bundle for PostgreSQL users

Then lets apply updates to the database schema, attention this might take a bit if you got a big database already.

RAILS_ENV=production bundle exec rake db:migrate # As always add DB=postgres to the command if you're a PostgreSQL user

Update the static content:

bundle exec rake assets:precompile

Now you need to restart Diaspora. To do this with the standard startup method you need to get to the place where you run ./script/server, hit Ctrl+C and run it again.

Updating a development install

Just checkout the develop branch, pull (from upstream), rebundle and migrate the database:

cd diaspora
git checkout develop
git pull # Or git pull upstream develop if you cloned from your fork
bundle # Or DB=postgres bundle if you use PostgreSQL
rake db:migrate