Deploying a production server requires additional setup steps.


  1. Change your SECRET_KEY and WEB_MGR_API_KEY to unique (and hopefully unguessable) strings in your

  2. Change the ownership of the whoosh_index directory to apache

    chown apache:apache whoosh_index/
  3. Ensure the server has the ability to send emails or you have access to an SMTP server. Set ``EMAIL_HOST``, ``EMAIL_PORT``, and ``DEFAULT_FROM_EMAIL`` in For more complicated outgoing mail setups, please refer to the django email documentation.

  4. Configure the Django Cache Framework to use a production capable backend in By default Ganeti Web Manager is configured to use the LocMemCache but it is not recommended for production. Use Memcached or a similar backend.

    CACHES = {
        'default': {
            'BACKEND': 'django.core.cache.backends.locmem.LocMemCache',
  5. For versions >= 0.5 you may need to add the full filesystem path to your templates directory to ``TEMPLATE_DIRS`` and remove the relative reference to ``’templates’``. We’ve had issues using wsgi not working correctly unless this change has been made.



  1. Set VNC_PROXY to the hostname of your VNC AuthProxy server in The VNC AuthProxy does not need to run on the same server as Ganeti Web Manager.

    VNC_PROXY = ''

SSH Keys

Project Versions

Table Of Contents

Previous topic


Next topic


This Page