django-windows-tools 0.2

Configuration

The service.ini is a configuration file that looks like the following:

[services]
# Services to be run on all machines
run=celeryd
clean=d:\logs\celery.log

[BEATSERVER]
# There should be only one machine with the celerybeat service
run=celeryd celerybeat
clean=d:\logs\celerybeat.pid;d:\logs\beat.log;d:\logs\celery.log

[celeryd]
command=celeryd
parameters=-f d:\logs\celery.log -l info

[celerybeat]
command=celerybeat
parameters=-f d:\logs\beat.log -l info --pidfile=d:\logs\celerybeat.pid

[runserver]
# Runs the debug server and listen on port 8000
# This one is just an example to show that any manage command can be used
command=runserver
parameters=--noreload --insecure 0.0.0.0:8000

[log]
filename=d:\logs\service.log
level=INFO

The services section contains :

• The list of background commands to run in the run directive.

• The list of files to delete when refreshed or stopped in the clean directive.

You can have several services sections in the same configuration file for different host servers. The Windows Service will try to find the section which name matches the name of the current server and will fallback to the services section if it does not find it. This allows you to deploy the same configuration file on serveral machines but only have one machine run the celery beat background process. In the preceding configuration, only the server named BEATSERVER will run the celerybeat command. The other ones will only run the celeryd command.

For each command name specified in the run directive, there must be a matching configuration section. The section contains two directives:

• command specifies the manage.py command to run.

• parameters specifies the parameters to the command.

In the previous configuration file, the celeryd configuration will spawn a process that will run the same command as :

D:\sites\mydjangoapp> python manage.py celeryd -f d:\logs\celery.log -l info

Lastly, the log section defines the log level and the the log destination file for the Windows Service.

Installation and start

The windows service is installed with the following command (run with Administrator privileges) :

D:\sites\mydjangoapp> python service.py --startup=auto install

It is started and stopped with the commands:

D:\sites\mydjangoapp> python service.py start
D:\sites\mydjangoapp> python service.py stop

It can be removed with the following commands:

D:\sites\mydjangoapp> python service.py remove

The Windows Service monitor changes to the service.ini configuration file. In case it is modified, the service does the following:

• Stop the background processes.

• Reread the configuration file.

• Start the background processes.

Customization

The winservice_install management command provides several options allowing to customize the name of the web service or of the script name. To obtain information about them, type:

D:\sites\mydjangoapp> python help winservice_install