****** GUI Installation ******

Be sure you have $LANG defined in your environment, as in

If you are running FreeBSD, django-admin is actually invoked as django-admin.py

  export LANG=en_US.UTF-8

Then create the initial tables

  $ django-admin syncdb --pythonpath /usr/local/etc/rpki --settings=settings

Answer "yes" when asked if you want to create superuser Enter username for
superuser Enter password

If you need to create superuser, you can

  $ django-admin createsuperuser --pythonpath /usr/local/etc/rpki --
  settings=settings

If you need to change superuser's password

  $ django-admin changepassword --settings=settings --pythonpath=/usr/local/
  etc/rpki <username>

Now configure apache, using /usr/local/etc/rpki/apache.conf, e.g.

  $ cp apache.conf /usr/local/etc/apache22/Includes/rpki.conf

You can put it in a virtual host if you wish.

Restart apache

  $ apachectl restart

Go to the URL for your web server and enter the superuser and password in login
form.

If you've only done the above bootstrap, there will only be a single handle to
manage, so the GUI will automatically bring you to the dashboard for that
handle.

****** GUI Installation to Work With rootd ******

Some of the commands depend on whether your are upgrading your existing
database, or starting a new installation from scratch.

[All users] First step is you will need to install Django South. For FreeBSD
this is /usr/ports/databases/py-south.

The code is currently in the tk316 branch, so in order to play, you will need
to check it out:

  $ svn co https://subvert-rpki.hactrn.net/branches/tk316
  $ cd tk316
  $ ./configure
  $ make
  $ make install

[Upgrading users] You will need to edit /usr/local/etc/rpki/settings.py and add
'south' to the INSTALLED_APPS list. See /usr/local/etc/rpki/settings.py.new for
an example (we don't automatically overwrite settings.py).

[All users] Run syncdb:

  $ django-admin syncdb --pythonpath=/usr/local/etc/rpki --settings=settings

Verify that Django South is installed:

  $ django-admin migrate --list --pythonpath=/usr/local/etc/rpki --
  settings=settings

[Upgrading Users] Since you already have an existing db, you need to fake doing
the initial migration step:

  $ django-admin migrate app 0001 --fake --pythonpath=/usr/local/etc/rpki --
  settings=settings

[All users] Perform the database migrations new to this release:

  $ django-admin migrate app --pythonpath=/usr/local/etc/rpki --
  settings=settings

[All users] Restart apache so that the web portal picks up the newly installed
code:

  $ apachectl restart

Now head back to the gui. Click on the 'refresh' link when viewing the altCA
dashboard, and it should now pick up the resources from the root cert.

****** Using the GUI ******

****** GUI Examples ******

***** Logging in to the GUI *****

 01-login.jpg

***** The Dashboard - Let's Make a ROA *****

 02-dashboard.jpg

***** ROA List Currently Empty, So Let's Create One *****

 03-roas.jpg

***** Choose an AS and Prefix - Let MaxLen? Default *****

 04-create-roa.jpg

***** What Will the Consequences Be? - Confirm OK *****

 05-are-you-sure.jpg

***** Now We Can See ROAs - Let's Look at Routes *****

      06-roa-list.jpg

***** Real Effect on Routing Table *****

 07-route view.jpg

***** Ghostbusters etc. are Similar *****