...
Download the COmanage Registry source files somewhere into the file system. The location you put the files does not have to be the location from which the files are served by the web server. Create a symlink to the directory called registry-sourcecurrent (or something similar):
| Code Block |
|---|
$ mkdir /srv/comanage $ cd /srv/comanage $ wget https://github.com/Internet2/comanage-registry/archive/1.0.0.tar.gz $ tar xzf 1.0.0.tar.gz $ ln -s comanage-registry-1.0.0 registry-sourcecurrent |
Downloading the Latest Master
...
Configure your web server to deliver the registry at a suitable URL such as https://some-vo.org/registry. A simple strategy to accomplish this when running under the Apache web server is to create a symlink in the DocumentRoot named registry that points to the directory .../registry-sourcecurrent/app/webroot:
| Code Block |
|---|
$ cd /var/www/html $ ln -s /path/to/registry-sourcecurrent/app/webroot registry |
The preferred path /var/www or /var/www/html may vary according to your operating system, distribution, or web server configuration.
| Note | ||
|---|---|---|
| ||
COmanage Registry currently assumes it is installed at the URL path |
...
You should verify that the web server will not deliver unprocessed files, especially configuration files such as the database configuration file (ie: https://some-vo.org/registry/app/configConfig/database.php). By default, these files will not be delivered.
...
The basic required structure for the tmp directory is included in app/tmp.dist. Be sure to replicate this in the target location.
| Code Block |
|---|
$ cd registry-sourcecurrent/app $ sudo cp -r tmp.dist /var/cache/registry $ sudo chown -R $HTTPUSER /var/cache/registry $ sudo chmod 700 /var/cache/registry $ cd registry-sourcecurrent/local $ ln -s /var/cache/registry tmp |
...