diff options
| author | RPKI Documentation Robot <docbot@rpki.net> | 2013-03-01 22:00:09 +0000 |
|---|---|---|
| committer | RPKI Documentation Robot <docbot@rpki.net> | 2013-03-01 22:00:09 +0000 |
| commit | d472f3f70215099c7945632e1e425b8abc9c7f10 (patch) | |
| tree | dbbde35cff389ccc5f9f166584e29526ee95a5b5 /doc/doc.RPKI.CA.UI.GUI | |
| parent | f5210c1f791ab21ac8c2ebb39a63f4ec780a2a56 (diff) | |
Automatic pull of documentation from Wiki.
svn path=/trunk/; revision=5094
Diffstat (limited to 'doc/doc.RPKI.CA.UI.GUI')
| -rw-r--r-- | doc/doc.RPKI.CA.UI.GUI | 23 |
1 files changed, 23 insertions, 0 deletions
diff --git a/doc/doc.RPKI.CA.UI.GUI b/doc/doc.RPKI.CA.UI.GUI index 116bd0b4..6c41c58d 100644 --- a/doc/doc.RPKI.CA.UI.GUI +++ b/doc/doc.RPKI.CA.UI.GUI @@ -33,6 +33,25 @@ you upgrade. $ rpki-manage migrate app 0001 --fake +If you are unsure whether or not you have previously run this command, you can +verify with the following command: + + $ rpki-manage migrate --list + + app + (*) 0001_initial + (*) 0002_auto__add_field_resourcecert_conf + (*) 0003_set_conf_from_parent + (*) 0004_auto__chg_field_resourcecert_conf + (*) 0005_auto__chg_field_resourcecert_parent + ( ) 0006_add_conf_acl + ( ) 0007_default_acls + +The migrations are an ordered list. The presence of the asterisk (*) indicates +that the migration has already been performed. ( ) indicates that the specific +migration has not yet been applied. In the example above, migrations 0001 +through 0005 have been applied, but 0006 and 0007 have not. + Now bring your database up to date with the current release: $ rpki-manage migrate app @@ -40,6 +59,10 @@ Now bring your database up to date with the current release: From this point on you will just need to run the latter command every time you upgrade. +Restart apache + + $ apachectl restart + ***** New Installation ***** **** Create the initial tables **** |