diff options
Diffstat (limited to 'doc/31.RPKI.CA.UI.GUI.Upgrading.BeforeMigration.md')
| -rw-r--r-- | doc/31.RPKI.CA.UI.GUI.Upgrading.BeforeMigration.md | 10 |
1 files changed, 6 insertions, 4 deletions
diff --git a/doc/31.RPKI.CA.UI.GUI.Upgrading.BeforeMigration.md b/doc/31.RPKI.CA.UI.GUI.Upgrading.BeforeMigration.md index 2de17368..a2df6f8f 100644 --- a/doc/31.RPKI.CA.UI.GUI.Upgrading.BeforeMigration.md +++ b/doc/31.RPKI.CA.UI.GUI.Upgrading.BeforeMigration.md @@ -3,9 +3,9 @@ This page documents the steps required to upgrade the web portal when you have a previous version of the software install **prior to migration support via Django South**. Note that this is a special case and will not apply to most -situations (see doc/RPKI/CA/UI/GUI/Upgrading for the normal upgrade path). If -you have already performed the steps on this page previously, then it does not -apply to your situation. +situations (see [Upgrading][] for the normal upgrade +path). If you have already performed the steps on this page previously, then +it does not apply to your situation. If you are unsure whether or not you have previously run this command, you can verify with the following command: @@ -66,7 +66,7 @@ Now bring your database up to date with the current release: $ rpki-manage migrate From this point forward you will follow the steps in -doc/RPKI/CA/UI/GUI/Upgrading each time you upgrade. +[Upgrading][] each time you upgrade. ## Restart Apache @@ -74,3 +74,5 @@ In order to make Apache use the new version of the software, it must be restarted: $ apachectl restart + +[Upgrading]: 30.RPKI.CA.UI.GUI.Upgrading.md |