|dave ab57b9d03c||4 years ago|
|Dockerfile||4 years ago|
|README.md||4 years ago|
|cron.conf||4 years ago|
|crontab||4 years ago|
|default||4 years ago|
|nginx.conf||4 years ago|
|pisg.py||4 years ago|
|sshd.conf||4 years ago|
|start||4 years ago|
|supervisor.conf||4 years ago|
|znc.conf||4 years ago|
Suitable for creating docker containers running ZNC. Now with pisg!
docker build -t znc .
docker run -it -p 8022:22 -p 6667:6667 -p 80:80 znc /start
docker ps -a
docker start mycontainer
If you wish to preserve data outside the container, mount:
When you first run the image, you’ll be presented with two ways to configure znc:
If no import of existing znc data is available, the znc configuration will run. Set it up as needed; the port znc listens on must be exposed in the command used to start the container (-p 4421:4421 above). The final question asks if you want to start znc, choose
You may migrate an existing ZNC instance into this container by providing a tarball of the source .znc directory. The tarball should contain the .znc directory, only, with everything inside it. The start script will prompt you to insert the .tar.gz file.
This container creates pisg-style channel statistics (example) for any ZNC users with the “log” module enabled. The stats are regenerated nightly and nginx serves the files on port 80 with a directory structure like this:
The channel information is private, nginx is configured with HTTP basic authentication; the password is prompted for during setup.
Individual channel statistic files can be made public by symlinking each, for example, to /home/znc/pisg/output/.pub/mychannel.html, which is public at http://server-ip/pub/mychannel.html. Directory listing for /pub/ is disabled.