idhub-docker/.env.example

# ORCHESTRA
####

#ORCHESTRA_SECRET_KEY='uncomment-it-and-fill-this'

# MUSICIAN
####

#MUSICIAN_SECRET_KEY='uncomment-it-and-fill-this'
# specially useful if you want to deploy in a specific domain
#MUSICIAN_API_BASE_URL='https://orchestra.example.org'
#MUSICIAN_ALLOWED_HOSTS='musician.example.org'
# IDHUB
####

IDHUB_TIME_ZONE='Europe/Madrid'
#IDHUB_SECRET_KEY='uncomment-it-and-fill-this'
# enable dev flags when DEVELOPMENT deployment
IDHUB_DEPLOYMENT='DEVELOPMENT'
# adapt to your domain in a production/reverse proxy env
IDHUB_CSRF_TRUSTED_ORIGINS='https://idhub.example.org'

# fill this section with your email credentials
IDHUB_DEFAULT_FROM_EMAIL="user@example.org"
IDHUB_EMAIL_HOST="smtp.example.org"
IDHUB_EMAIL_HOST_USER="smtp_user"
IDHUB_EMAIL_HOST_PASSWORD="smtp_passwd"
IDHUB_EMAIL_PORT=25
IDHUB_EMAIL_USE_TLS=True
IDHUB_EMAIL_BACKEND="django.core.mail.backends.smtp.EmailBackend"

# replace with production data
#   this is used when IDHUB_DEPLOYMENT is not equal to DEVELOPMENT
IDHUB_USER='admin'
IDHUB_PASSWD='admin'
IDHUB_EMAIL='admin@example.org'
orchestra & musician: use env namespace 2023-10-31 09:44:46 +00:00			`# ORCHESTRA`
			`####`
init with previous work this repo is a reinitialization with a change in the concept previous repo had git subtree of django-musician and django-orchestra, that was too static for our interest next approach is a script that pulls git repos, and that would be needed if you want to build everything, if not, just with the docker compose you would have enough for running the containers, hence, downloading the images from the docker registry 2023-10-10 08:07:46 +00:00
orchestra & musician: use env namespace 2023-10-31 09:44:46 +00:00			`#ORCHESTRA_SECRET_KEY='uncomment-it-and-fill-this'`

			`# MUSICIAN`
			`####`

			`#MUSICIAN_SECRET_KEY='uncomment-it-and-fill-this'`
init with previous work this repo is a reinitialization with a change in the concept previous repo had git subtree of django-musician and django-orchestra, that was too static for our interest next approach is a script that pulls git repos, and that would be needed if you want to build everything, if not, just with the docker compose you would have enough for running the containers, hence, downloading the images from the docker registry 2023-10-10 08:07:46 +00:00			`# specially useful if you want to deploy in a specific domain`
orchestra & musician: use env namespace 2023-10-31 09:44:46 +00:00			`#MUSICIAN_API_BASE_URL='https://orchestra.example.org'`
			`#MUSICIAN_ALLOWED_HOSTS='musician.example.org'`
idhub: add envs for idhub namespace 2023-11-03 09:12:09 +00:00			`# IDHUB`
			`####`

idhub: add env vars for email credentials 2023-11-14 10:28:58 +00:00			`IDHUB_TIME_ZONE='Europe/Madrid'`
idhub: add envs for idhub namespace 2023-11-03 09:12:09 +00:00			`#IDHUB_SECRET_KEY='uncomment-it-and-fill-this'`
			`# enable dev flags when DEVELOPMENT deployment`
			`IDHUB_DEPLOYMENT='DEVELOPMENT'`
idhub: add CSRF_TRUSTED_ORIGINS env var 2023-11-03 09:11:30 +00:00			`# adapt to your domain in a production/reverse proxy env`
			`IDHUB_CSRF_TRUSTED_ORIGINS='https://idhub.example.org'`
idhub: add env vars for email credentials 2023-11-14 10:28:58 +00:00
			`# fill this section with your email credentials`
			`IDHUB_DEFAULT_FROM_EMAIL="user@example.org"`
			`IDHUB_EMAIL_HOST="smtp.example.org"`
			`IDHUB_EMAIL_HOST_USER="smtp_user"`
			`IDHUB_EMAIL_HOST_PASSWORD="smtp_passwd"`
			`IDHUB_EMAIL_PORT=25`
			`IDHUB_EMAIL_USE_TLS=True`
			`IDHUB_EMAIL_BACKEND="django.core.mail.backends.smtp.EmailBackend"`
docker: put init data as part of dev deployment use django default env vars on a production deployment 2023-11-16 16:03:19 +00:00
			`# replace with production data`
			`# this is used when IDHUB_DEPLOYMENT is not equal to DEVELOPMENT`
			`IDHUB_USER='admin'`
			`IDHUB_PASSWD='admin'`
			`IDHUB_EMAIL='admin@example.org'`