How to upgrade

If you are upgrading Munkireport from a previous version, there are some things to keep in mind.

Back up your database

Although we try to make upgrading as smooth as possible, there may be cases where the upgrade (or the one who makes the upgrade) does bad things to your database. Use a backup strategy that fits the database backend you are using.

SQLite
The standard location of the SQLite database is in the app directory, if you're upgrading by downloading the new version of Munkireport and copying the files over the previous version, this database is going to be lost. Fortunately, backing up a SQLite database is easy: just save a copy of app/db/db.sqlite to a safe place.

MySQL
You can backup a MySQL database using different methods:

• via the command line using mysqldump
• with phpMyAdmin if you have that installed
• with a fat client like Sequel Pro

If your database does get deleted, you can also just wait until your clients fill it up again

Backup your config

Copy config.php to a safe place.

Use GIT

The easiest and safest way to upgrade is using git. When you use git, the SQLite database does not get overwritten and your config.php file stays intact. With git it is easy to revert the update if things don't work out so well. The following assumes that you set up munkireport with git (git clone https://github.com/munkireport/munkireport-php.git)

To checkout the latest master:

git checkout master
git pull

Copy files

If you can't use git, then you can copy the new files to the proper location. If you're running Munkireport from a subdirectory called 'munkireport', you can rename that directory to 'munkireport.old'. Then you put the new version up under 'munkireport' and copy config.php and optionally db.sqlite to 'munkireport'.