2. Adapt your (inventory-)config with ``nano ~/otree-ansible/group_vars/otree_servers.yml`` from the provided example accordingly (press "Strg-x", then "j" to save):
```
otree_master: "otree1"
# which otree instance should be delivered as default
otree_domain: "otree.company.org"
otree_master: "otree1"
# fqdn of the otree server
otree_group_name: "otreeusers"
otree_domain: "otree.company.org"
# linux group for the otree users
otree_group_name: "otreeusers"
# dict of users for the available otree instances
otree_users:
# list of users for the available otree instances
otree1:
# linux username
override: yes
otree1:
# should an existing otree environment be overriden
pre_release: no
# should the pre-release version of otree be installed
redis: "redis://localhost:6379/1"
override: yes
# redis queue. Note don't use a slot twice, there are 16 slots available (0-15)
database: "sqlite:////home/otree1/db.sqlite3"
redis: "redis://localhost:6379/1"
# which database should be used. Examples: "postgres://USER:PASSWORD@HOST:PORT/NAME" or "sqlite:////home/user/db.sqlite3"
admin_pw: "mysecretpw1"
database: "sqlite:////home/otree1/db.sqlite3"
# otree admin password
auth_level: "STUDY"
admin_pw: "mysecretpw1"
# auth level, possible values: "STUDY", "DEMO"
secret_key: "safaho9awefzuwf"
auth_level: "STUDY"
# django secret key, use differet in different instances
production: "1"
secret_key: "safaho9awefzuwf"
# LOG-LEVEL, set to None ("production: ") to enable further debug messages.
