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

doc/upgrading: mention 1.4.x

Browse Source 
fixes #1380
This commit is contained in:
Thomas Gelf 2018-02-05 14:34:52 +01:00
parent 081ddf5e85
commit 0e0014d452
1 changed files with 11 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
doc/05-Upgrading.md
View File

@ -16,6 +16,7 @@ you will be told so in your frontend.
Please read more about:
* [Database Backup](#backup-first)
* [Upgrading to 1.4.x](#upgrade-to-1.4.x)
* [Upgrading to 1.3.0](#upgrade-to-1.3.0)
* [Upgrading to 1.2.0](#upgrade-to-1.2.0)
* [Upgrading to 1.1.0](#upgrade-to-1.1.0)
@ -35,11 +36,19 @@ 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
pending database migrations to an imported old database snapshot.
<a name="upgrade-to-1.3.0"></a>Upgrading to 1.3.0
<a name="upgrade-to-1.4.x"></a>Upgrading to 1.4.x
-------------------------------------------------
There is nothing special to take care of. In case you are running 1.3.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.4.x` in case you installed Director from
GIT.
<a name="upgrade-to-1.3.x"></a>Upgrading to 1.3.x
-------------------------------------------------
In case you are running 1.2.0 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.3.0`
replace the Director module folder with the new one. Or to run `git checkout v1.3.x`
in case you installed Director from GIT.
When running Director since 1.1.0 or earlier on PostgreSQL, you might not yet