Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
O
otree-ansible
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Deploy
Releases
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
wiso-forschungslabor
otree-ansible
Commits
16a319ba
Commit
16a319ba
authored
5 years ago
by
Gallenkamp, Fabian
Browse files
Options
Downloads
Patches
Plain Diff
First draft of readme.
parent
ac249ba8
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+24
-0
24 additions, 0 deletions
README.md
with
24 additions
and
0 deletions
README.md
+
24
−
0
View file @
16a319ba
# ansible script to setup otree instances
## preparation
### place ssl/tls certificates and key-file (unfortunately not scriptable)
### install ansible and clone this project
``sudo apt install ansible git``
``git clone https://gitlab.rrz.uni-hamburg.de/bax1489/otree-ansible.git``
### configure playbook
Adapt your
``group_vars/otree_servers.yml``
from the provided example accordingly:
### (optional) upload otree project
If no git-repository with your otree project is provided, you can place a copy in
``files/<otree_username>/``
.
And now run the playbook.
## change the configuration
Adapt
``group_vars/otree_servers.yml``
and run the playbook again
## run the playbook
Run
``ansible-playbook site.yml``
.
\ No newline at end of file
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment