- Init and Run Control Scripts
- Enable MD5 authentication to PostgreSQL
- Relocating the Installation
- Pass Options to the Web Frontend Daemon
- Non-root Hosting
- Listening Port for the Web Frontend
- Listening Address for the Web Frontend
- Behind a Proxy
- SSL Support
- Further Reading...
App::Netdisco::Manual::Deployment - Tips and Tricks for Deployment
Init and Run Control Scripts
The Netdisco applications will generate RC scripts suitable for Linux systems:
bin/netdisco-web get_init_file bin/netdisco-daemon get_init_file
If you'd like to send a patch for BSD, please submit it against the Daemon::Control distribution.
Enable MD5 authentication to PostgreSQL
Some installations of PostgreSQL don't have MD5 authentication enabled by default, which blocks database connections with the default Netdisco configuration.
If your database and Netdisco are on the same system, then the easiest solution is to comment out the "
host:" line in your
Alternatively, reconfigure PostgreSQL to permit MD5 auth for TCP connections by adding the following to your system's "
pg_hba.conf" file (and restarting the database service):
# TYPE DATABASE USER ADDRESS METHOD host all all 127.0.0.1/32 md5
Relocating the Installation
The installation process installs Netdisco self-contained to your home directory. The target directory can easily be changed by setting the
NETDISCO_HOME environment variable, for example:
Obviously, you'll need to substitute this wherever you see "
~" in the installation instructions. The Netdisco application will use this setting itself to locate files and configuration.
Pass Options to the Web Frontend Daemon
Simply add any options after the "
start" command. See other sections of this document for some examples.
Netdisco will assume its web site is hosted at the apex of your server - that is, the document root. To relocate the web application, pass the
--path parameter to the web startup script:
~/bin/netdisco-web start --path=/netdisco2
Alternatively, can set the
path configuration option in your
Listening Port for the Web Frontend
--port parameter to any of the web scripts. For example:
~/bin/netdisco-web start --port=8080
Listening Address for the Web Frontend
--host parameter to any of the web scripts. For example:
~/bin/netdisco-web start --host=127.0.0.1
Behind a Proxy
By default the web application daemon starts listening on port 5000 and goes into the background. This is ideal for hosting behind a web proxy (e.g. Apache with
After enabling the
proxy_http modules in Apache, a suitable configuration would be:
ProxyPreserveHost On ProxyPass / http://localhost:5000/ retry=0 timeout=60 ProxyPassReverse / http://localhost:5000/ ProxyRequests Off <Proxy *> Order allow,deny Allow from all </Proxy>
To combine this with Non-root Hosting as above, simply change the paths referenced in the configuration, and set
path in your
deployment.yml as discussed above. Note there is no trailing slash in the Apache config:
ProxyPass /netdisco2 http://localhost:5000/netdisco2 retry=0 timeout=60 ProxyPassReverse /netdisco2 http://localhost:5000/netdisco2
To delegate user authentication to Apache, use the
trust_x_remote_user settings. See App::Netdisco::Manual::Configuration for more details.
There is no SSL support in the built-in web server. This is because it's not straightforward to support all the SSL options, and using port 443 requires root privilege, which the Netdisco application should not have.
You are instead recommended to run
netdisco-web behind a reverse proxy as described elsewhere in this document. Apache can easily act as an SSL reverse proxy.