42 lines
2 KiB
YAML
42 lines
2 KiB
YAML
---
|
|
# Copy this file to inventory.yml (git-ignored) and fill in your real
|
|
# hosts. Each entry under hosts: is an independent deployment - see the
|
|
# README's "Per-deployment configuration" section for what each var means.
|
|
|
|
toolshed:
|
|
hosts:
|
|
my-server:
|
|
ansible_host: 203.0.113.10
|
|
ansible_user: deploy
|
|
# toolshed_domain is the "web domain" - see the README's DNS section
|
|
# for how this relates to the separate "handle domain" your users
|
|
# log in with (user@yourtoolshed.tld).
|
|
toolshed_domain: toolshed.webdomain.tld
|
|
# Optional - only needed if the handle domain differs from the web
|
|
# domain above. Omit it entirely when they're the same.
|
|
toolshed_handle_domain: yourtoolshed.tld
|
|
toolshed_repo_url: git@example.com:your-org/toolshed.git
|
|
# Optional - branch, tag or commit to deploy. Defaults to "stable".
|
|
toolshed_version: stable
|
|
# true if something in front of this host already terminates TLS
|
|
# (reverse proxy/load balancer), false if this nginx must do it itself.
|
|
behind_tls_proxy: false
|
|
# Required whenever behind_tls_proxy is false: the playbook obtains
|
|
# its own Let's Encrypt certificate via certbot, which needs an
|
|
# account email for renewal notices.
|
|
toolshed_letsencrypt_email: admin@example.com
|
|
|
|
# A second, unrelated deployment behind an existing TLS-terminating
|
|
# proxy - remove this if you only run one instance. Here the handle
|
|
# domain and web domain are the same, so toolshed_handle_domain is
|
|
# simply omitted, and toolshed_letsencrypt_email isn't needed since
|
|
# this nginx never handles TLS itself.
|
|
my-other-server:
|
|
ansible_host: my-other-server.example.com
|
|
ansible_user: deploy
|
|
toolshed_domain: toolshed.example.com
|
|
toolshed_repo_url: git@example.com:your-org/toolshed.git
|
|
behind_tls_proxy: true
|
|
# Only needed if the proxy in front forwards to something other than
|
|
# port 80 on this host.
|
|
http_port: 8080
|