Configuring your webserver

For now we support nginx and apache webservers through automated solutions like docker and a crontab configuration.

Docker (Culturize-Back-End-Docker)

Pros & Cons

Pros

• The docker configuration can be installed alongside an already running webserver and is easy to remove
• Nginx and Apache webservers supported
• From the second you push newly created or updated PIDs to your code repository, they will be live

Cons

• Dependant of Docker and Docker Compose
• Only works with Apache .htaccess-files

Requirements

• Docker
• Docker-Compose

Configuration

Go to the README of the (CultURIze-Back-End-Docker repository) for installation and configuration instructions.

Unix + git + crontab (Culturize & Crontab)

Pros & Cons

Pros

• Only uses standard unix tools that should be available on every webserver
• Easy setup
• Can be used with Nginx configuration files and Apache .htaccess files

Cons

• Quick and dirty, dirty being the fact the crontab keeps sending requests to GitHub even when nothing has changed in the repository
• No "immediate" update of the PIDs

Requirements

• A GitHub account
• Git
• Apache or Nginx web server

Configuration

You can find the complete documentation for setting up automated configuration for Culturize with crontab on this page Culturize & Crontab