Clone this wiki locally
It should always be possible to upgrade to the next major version in one step.
So, it should be possible to upgrade from any version 6 to version 7, but not straight to version 8.
This limitations was chosen to avoid having to keep around and maintain an ever increasing baggage of migrations.
It is highly recommended you upgrade regularly, since the longer you wait, the more steps the upgrade will take. Also, upgrading ensures security issues will be fixed.
Upgrading to upcoming Publify 9
Note: Publify 9 is not officially out yet, so running it in production is not yet recommended!
Publify 9 uses the default Rails system for setting secret values. This means that you'll have to set the
SECRET_KEY_BASE environment value to some secret value. You can do this by configuring your web server to set it, by using a tool like
dotenv, or, on Heroku, by adding it to the set of values using the web interface.
For the smoothest transition, you can look in your existing
config/secret.token for the exisiting secret and re-use that. This will keep sessions and Devise' password reset tokens working.
Upgrading to the latest version of Publify 8
If you're already using a version of Publify in the 8.x series, you can upgrade to its latest version using the general upgrade instructions below.
Please also read the relevant release announcements listed in the next section.
Upgrading from Publify 7 to Publify 8
From Publify 7 (either 7.0.0 or 7.1.0), you should be able to upgrade to any version in the 8.x series.
Then, see below for general upgrade instructions.
Upgrading from Typo 6 to Publify 7.
From Typo 6, you first have to migrate to Publify 7.
Make sure you first read the announcement of the change from Typo to Publify.
Then, see below for general instructions.
Upgrading from earlier versions of Typo
You must first upgrade to Typo 6.
First, stop your blog installation. We don't want any changes to the database while upgrading.
In these instructions, I'm going to assume you're running your blog on a production environment. If not, replace
production with your chosen environment.
Upgrading the Files
First, unpack the tarball to a new directory. I'm assuming your upgrading to release 8.0.1. If not, replace the release file name with the actual file name.
$ tar xvzf publify-8.0.1.tar.gz
Next, rename your whole blog directory to some safe place and replace it with the new one.
$ mv blog_path old_blog $ mv publify-8.0.1 blog_path
Move your old files, theme, database.yml and any file you want to keep to your new install.
$ mv old_blog/themes/yourtheme blog_path/themes $ mv old_blog/public/files/ blog_path/public $ mv old_blog/config/database.yml blog_path/config $ ...
Check that your Web server has the right to write your blog install, then restart your blog instance.
Upgrading the Database
Login in to your blog admin using your favourite web browser. You'll access to the database migration page. Just click on the "migrate" button.
If something goes wrong, go back to your terminal, and run
$ cd typo_path $ RAILS_ENV=production rake db:migrate