Marty Oehme
6b4c4ccde4
Previously every deployment (even just for a single tag, such as `ansible-playbook site.yml --tags landingpage`) would have the caddy deployment in its dependency. That meant in effect whenever there was an updated caddy image, the role would update it and we would lose all previous caddy configuration - which in turn would necessitate a complete redeploymnet of all steps. This is now not the case anymore. |
||
|---|---|---|
| .. | ||
| defaults | ||
| handlers | ||
| meta | ||
| tasks | ||
| templates | ||
| vars | ||
| README.md | ||
wallabag
A very simple service application stack role which can be used to base other roles off of. Contains only a single deployed image and a couple of simple variables to set.
Variables
wallabag_upstream_file_dir: "{{ docker_stack_files_dir }}/{{ stack_name }}"
The on-target directory where the proxy configuration file should be stashed.
wallabag_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.
wallabag_version: latest
The docker image version to be used in stack creation.
Internal variables
stack:
name: wallabag
compose: "{{ lookup('template', 'docker-stack.yml.j2') | from_yaml }}"
The name of the stack to be provisioned and the compose file to be used. See caddy ReadMe for configuration.
stack_image: "wallabag/wallabag"
The docker hub image to be use in provisioning.