An interactive campaign manager for the game "Monster", by Kingdom Death. Development blog at This project has no affiliation with Kingdom Death and is a totally independent, fan-maintained project.
JavaScript Python CSS Other
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
v1 r2.4.268 Feb 26, 2017
v2 missed this in my last Feb 26, 2017
.gitignore interim commit to add the login route Feb 11, 2017 add handling for monster name postscript comment Oct 22, 2016


Follow this guide to install and configure the manager for the first time on a Debian system. Production runs on Ubuntu LTS.

Start from bare metal on deb/ubuntu (do this in order):

# apt-get install git mongodb-server nginx python2.7 python-dev python-setuptools gcc python-imaging python-gridfs  

python dependencies

# easy_install python-dateutil python-daemon psutil lockfile pymongo pydns validate-email user-agents xlwt requests

Now, as the non-root user who is going to run the Manager's processes, do this:

# exit
$ cd
$ git clone 

Assuming that the user who wants to run the application is toconnell, and that you're ONLY using this server for kdm-manager, do this as root:

# ln -s /home/toconnell/kdm-manager/v1/init_script /etc/init.d/kdm-manager  
# update-rc.d -f kdm-manager defaults  
# /etc/init.d/nginx stop
# rm /etc/nginx/sites-enabled/default
# ln -s /home/toconnell/kdm-manager/v1/nginx/default /etc/nginx/sites-enabled/kdm-manager_dev

The file /v1/nginx/production that ships with the repo contains all of the media (static content) server and redirect configs that facilitate the production deployment of the Manager.

If you're just doing some dev/support work, you don't need all of that and you should stick with /v1/nginx/default as your webserver config.

Restarting nginx and running the Manager's init script for the first time will create the log and lockfile directories. it should also start the server on the port specified in settings.cfg:

# /etc/init.d/nginx start
# /etc/init.d/kdm-manager start  

Following that, the Manager will be running and it should start automatically on reboot.

Finally, please review the wiki for additional information on installation and deployment, including troubleshooting tips: