ADMIN_USER. In this setup, data and results are owned by the
ADMIN_USERyet applications can be triggered by any user.
DEFAULT_LINUX_GROUPin the Isabl CLI client object (you can do so by updating your client
ISABL_CLIENT_IDfrom the Django admin website). For example:
PYTHONPATHenvironment variable or pip installing locally your apps repo:
Can Download Resultspermission to configure what users can download analyses results in your Isabl instance.
production.ymlfile in the root of this project. Keep note of how it provides configuration for the following services:
django: your application running behind
postgres: PostgreSQL database with the application's relational data;
redis: Redis instance for caching;
caddy: Caddy web server with HTTPS on by default.
y) there are three more services:
celeryworkerrunning a Celery worker process;
celerybeatrunning a Celery beat process;
DJANGO_ALLOWED_HOSTSenvironment variable (see settings) before you deploy your website. Failure to do this will mean you will not have access to your website through the HTTP protocol.
DOMAIN_NAMEconfiguration has the
https://schema prepended in the caddy environment file
.envs/.production/.caddy(see this ticket to learn more). Then include the following configuration in
compose/production/caddy/Caddyfilein order to use a self signed certificate:
production_postgres_datavolume by default. Change that if you want something else and make sure to make backups since this is not done automatically.