Marty Oehme
3ee003f94c
Removed setting the landingpage upstream accidentally, switched its alias to blog instead. |
||
|---|---|---|
| .. | ||
| defaults | ||
| handlers | ||
| meta | ||
| tasks | ||
| templates | ||
| vars | ||
| README.md | ||
landingpage
The public face of my server. Not much to see here honestly, just a few simple lines of html explaining what this server is about and how to contact me.
I don't see anybody else benefiting massively from this role but me, but if you want the same web presence go for it I suppose 😉
Defaults
landingpage_upstream_file_dir: "{{ docker_stack_files_dir }}/{{ stack_name }}"
The on-target directory where the proxy configuration file should be stashed.
landingpage_use_https: true
Whether the service should be reachable through http (port 80) or through https (port 443) and provision an https certificate. Usually you will want this to stay true.
landingpage_version: latest
The docker image version to be used in stack creation.
subdomain_alias: www
If the deployed container should be served over a uri that is not the stack name.
By default, it will be set to www.yourdomain.com -
if this option is not set it will be served on landingpage.yourdomain.com instead.