Drop in documentation extracted from wiki.rpki.net. See README for details.

1 files changed, 0 insertions, 37 deletions

diff --git a/doc/doc.RPKI.CA.UI.GUI.Upgrading b/doc/doc.RPKI.CA.UI.GUI.Upgrading
deleted file mode 100644
index 4d17d910..00000000
--- a/doc/doc.RPKI.CA.UI.GUI.Upgrading
+++ /dev/null
@@ -1,37 +0,0 @@
-****** Upgrading from a Previous Version ******
-
-* See wiki:doc/RPKI/CA/UI/GUI/Upgrading/BeforeMigration for the special
-  situation where you are upgrading from a release prior to database migration
-  support being added.
-
-This page describes the steps you must take if you upgrading from a previous
-version of the software that is already installed on the system. If you are
-installing for the first time see doc/RPKI/CA/UI/GUI/Installing.
-
-Run the following commands at a shell prompt. Note that you do not need run
-these as the root user, any user with permission to read /etc/rpki.conf is
-sufficient.
-
-  rpki-manage syncdb
-  rpki-manage migrate
-
-Note that at the end of the syncdb output you will see the following message:
-
-  Not synced (use migrations):
-   - rpki.gui.app
-  (use ./manage.py migrate to migrate these)
-
-You should ignore the message about running ./manage.py since that script does
-not exist in our setup (we use rpki-manage instead`).
-
-***** Restart Apache *****
-
-In order to cause Apache to reload the web portal software using the newly
-installed software, it must be restarted. Execute the following command as root
-in a shell:
-
-  apachectl restart
-
-***** Next Step *****
-
-See doc/RPKI/CA/UI/GUI/Configuring