General remarks

Requirements

To use eventyay, you will need the following things:

  • Eventyay and the python packages it depends on

  • An WSGI application server (we recommend gunicorn)

  • A periodic task runner, e.g. cron

  • A database. This needs to be a SQL-based that is supported by Django. We highly recommend to either go for PostgreSQL. If you do not provide one, eventyay will run on SQLite, which is useful for evaluation and development purposes.

    Warning

    Do not ever use SQLite in production. It will break.

    Warning

    We recommend to use PostgreSQL.

  • A reverse proxy. eventyay needs to deliver some static content to your users (e.g. CSS, images, …). While eventyay is capable of doing this, having this handled by a proper web server like nginx or Apache will be much faster. Also, you need a proxying web server in front to provide SSL encryption.

    Warning

    Do not ever run without SSL in production. Your users deserve encrypted connections and thanks to Let’s Encrypt SSL certificates can be obtained for free these days.

  • A redis server. This will be used for caching, session storage and task queuing.

    Warning

    eventyay can run without redis, however this is only intended for development and should never be used in production.

  • Optionally: RabbitMQ or memcached. Both of them might provide speedups, but if they are not present, redis will take over their job.