Updating

New releases are installed from the admin, over the copy you have, with a backup first and a way back if anything fails. Nothing is ever installed without somebody asking.

Open Settings > Utilities > Update.

How an update works #

1. The release is downloaded and checked against the checksum in the release feed.
2. The database is dumped, and every file about to change is copied.
3. The files are swapped. The site is in maintenance for a few seconds, and scheduled tasks wait.
4. The database update runs on the new code. If anything fails, the files and the database are put back.

Never touched: the installer's files in config/ (your connection and keys) and everything under system/.

The feed is read once a day. Check for updates reads it now, and the screen shows the installed version, the available one and when it was last checked.

Installing an update #

1. Back up your own database as well, if you can. The screen has an I have a backup of the database of my own box.
2. Read the release notes on the Update screen.
3. Press Install next to the version. The screen lists anything that stops it from being installed yet.

Files you changed #

If you changed a file that the release also changes:

• it is replaced, and your copy is kept in the backup; or
• it is kept as you changed it, and the release's version is beside it with .lbm-new added; or
• if it is no longer in the release but you changed it, it is left in place.

The screen lists these after the update. Changes belong in your own templates or plugins where you can, so updates do not touch them.

Update channels #

Choose a channel on the Update screen:

If an update does not finish #

The Update screen says "Finishing the update" and offers Finish the update (to run the database update) or Go back to the old version. From the console:

php laika update:check      # read the release feed
php laika update:install    # install the available release
php laika update:finish     # run the database update after the files are in place
php laika update:rollback   # take the update back

If the screen reports database updates that have not run (the files were copied by hand, or an update was interrupted), run:

php laika migrate

Before you update a live site #

• Read the release notes.
• Update a staging copy first, with a developer licence.
• Choose a quiet hour: the site is unavailable for a few seconds.