tyler.durden/icingaweb2-module-director
1
0
Fork 0
mirror of https://github.com/Icinga/icingaweb2-module-director.git synced 2025-07-28 16:24:05 +02:00
Code Issues Packages Projects Releases Wiki Activity

doc/upgrading: new section for v1.5.x

Browse Source
This commit is contained in:
Thomas Gelf 2018-08-10 14:00:03 +02:00
parent 71cc5939d3
commit 46ba2f8366
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/05-Upgrading.md
View File

@ -16,6 +16,7 @@ you will be told so in your frontend.
Please read more about: Please read more about:
* [Database Backup](#backup-first) * [Database Backup](#backup-first)
* [Upgrading to 1.5.x](#upgrade-to-1.5.x)
* [Upgrading to 1.4.x](#upgrade-to-1.4.x) * [Upgrading to 1.4.x](#upgrade-to-1.4.x)
* [Upgrading to 1.3.0](#upgrade-to-1.3.0) * [Upgrading to 1.3.0](#upgrade-to-1.3.0)
* [Upgrading to 1.2.0](#upgrade-to-1.2.0) * [Upgrading to 1.2.0](#upgrade-to-1.2.0)
@ -36,6 +37,16 @@ use the tools provided by your database backend, like `mysqldump` or `pg_dump`.
Restoring from a backup is trivial, and Director will always be able to apply Restoring from a backup is trivial, and Director will always be able to apply
pending database migrations to an imported old database snapshot. pending database migrations to an imported old database snapshot.
<a name="upgrade-to-1.5.x"></a>Upgrading to 1.5.x
-------------------------------------------------
There is nothing special to take care of. In case you are running 1.4.x or any
GIT master since then, all you need is to replace the Director module folder
with the new one. Or to run git checkout v1.5.0 in case you installed Director
from GIT.
As always, you'll then be prompted to apply pending Database Migrations.
<a name="upgrade-to-1.4.x"></a>Upgrading to 1.4.x <a name="upgrade-to-1.4.x"></a>Upgrading to 1.4.x
------------------------------------------------- -------------------------------------------------