blob: 3ab90eea1095da0095af8ce4a57f748c53245531 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
|
$Id$
This file details how to use the rpkidemo script with the portal-gui.
requirements
============
- the portal-gui must be run using apache with mod_wsgi
Fedora:
$ yum install httpd mod_wsgi
setup
=====
- follow the steps in detailed in the README file to set up the portal-gui
for the self-hosted resource handle that will act as parent to all other
users.
- after running "make" in $top/portal-gui, there will be a file named
$top/portal-gui/apache/zmyrpki.conf. This is a configuration file for
apache which does most of the work configuring the portal-gui to run
under mod_wsgi.
Fedora:
cp $top/portal-gui/apache/zmyrpki.conf /etc/httpd/conf.d/
- edit `zmyrpki.conf' and change the URL to match your own environemnt. by
default it uses http://localhost/myrpki/, which is probably not what you
want.
- run the `adduser' script to configure the portal-gui with a new account. you
need to specify the user's parent on the command line, as this acts as an
implicit authorization when rpkidemo uploads its identity.xml.
testing with yamltest
=====================
- you can specify
CONFDIR=$top/rpkid/tests/yamltest.dir
to make the portal-gui be a front-end for the resource handles created by
a yamltest run.
- you will need to periodically run the lists_resources script in
$top/rpkid/tests/yamltest.dir/RIR
to update the portal-gui database with the current state of children and
received resources
- the web server runs as the `apache' user by default under Fedora, which won't
have permissions to write to the yamltest.dir directory. easiet thing to do
is chown the entire tree so that the `apache' user has full access:
# chown -R apache $top/rpkid/tests/yamltest.dir
|
