MALMan is a WSGI app
Getting the code
Create a directory to contain the program and get the source code:
mkdir -p /usr/local/share/webapps git clone git://github.com/voidwarranties/MALMan.git /usr/local/share/webapps/MALMan
From here on on I will assume you are located in the directory you installed MALMan in, so move into this directory.
Setting up the virtualenv and getting dependencies
You will need to have version 2 of python, pip and virtualenv installed on your system. On debian-based systems these are provided by the packages python, python-pip and python-virtualenv. If installing on Arch linux you will need the packages python2, python2-pip and python2-virtualenv and will have to substitute 'virtualenv-2' for 'virtualenv' in the following command.
Set up a isolated Python environment in the directory 'env'.
Fetch the latest version of distribute, which is needed to fetch some of the dependencies:
env/bin/pip install distribute --upgrade
Install the required python packages into the enviroment.
env/bin/pip install -r requirements.txt
Setting up the database
If you want to use sqlite skip this step.
If you want to use mysql create a new database with your favorite mysql client. For mysql you also have to install one more requirement:
env/bin/pip install MySQL-python==1.2.5
Copy MALMan.cfg.template to MALMan.cfg and fill in the database, SMTP and security parameters.
For development purposes you might want to use Python's SMTP debugging server:
python -m smtpd -n -c DebuggingServer localhost:1025
This will start an SMTP server on port 1025 of localhost. All mails sent will be displayed in the console output.
Before the first run
Test the database connection create the tables we need:
env/bin/python commands.py init_database
Running in debug mode
You should now be able to run MALMan in development mode. This isn't suitable for production use.
env/bin/python commands.py runserver
MALMan should be running locally on 0.0.0.0:5000.
Specify a host to make it accessible to other devices on the network:
env/bin/python commands.py runserver --host ::
Activating the first account
After registering a user's membership request will have to be accepted by an active member with member management permissions. With no one to activate the first user we will have to do this outside of MALMan:
env/bin/python commands.py confirm_email firstname.lastname@example.org env/bin/python commands.py activate_member email@example.com env/bin/python commands.py give_perm firstname.lastname@example.org members
This will accept the membership request of your first user and grant her membership management permissions, so further request can be handled through MALMan.
Running in production mode
Be sure to disable the DEBUG mode in MALMan/MALMan.cfg when running in production.
MALMan can run as a WSGI app under Apache or as a fastcgi app under various other web servers. A runner is provided for both (MALMan.wsgi and MALMan.fcgi).
Serve under apache
Include this in /etc/httpd/conf/httpd.conf:
LoadModule wsgi_module modules/mod_wsgi.so WSGIScriptAlias /MALMan /usr/local/share/webapps/MALMan/MALMan.wsgi <Directory /usr/local/share/webapps/MALMan> Order deny,allow Allow from all WSGIScriptReloading On </Directory>
This tells apache to load the wsgi module at /usr/local/share/webapps/MALMan/MALMan.wsgi and serve it under /MALMan.
Serve with Lighttpd
make a new file /etc/lighttpd/conf-available/15-fastcgi-MALMan.conf with this content:
fastcgi.server += ( "/MALMan" => (( "socket" => "/tmp/MALMan-fcgi.sock", "bin-path" => "/usr/local/share/webapps/MALMan/MALMan.fcgi", "check-local" => "disable", "max-procs" => 1 )) )
enable the new config:
change owner of the files to www-data:
chown www-data:www-data /usr/local/share/webapps/MALMan -R
service lighttpd restart
you can find your website at http://localhost/MALMan.fcgi (or using the ip / a linked domain if hosted remotely)