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 | ||
| files | ||
| handlers | ||
| meta | ||
| tasks | ||
| templates | ||
| vars | ||
| README.md | ||
forgejo
A relatively light-weight git server hosting.
Defaults
forgejo_upstream_file_dir: "{{ docker_stack_files_dir }}/{{ stack_name }}"
The on-target directory where the proxy configuration file should be stashed.
forgejo_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.
forgejo_version: latest
The docker image version to be used in stack creation.
subdomain_alias: git
If the deployed container should be served over a uri that is not the stack name.
By default, it will be set to git.yourdomain.com -
if this option is not set it will be served on forgejo.yourdomain.com instead.
For now forgejo will still need to be initially set up after installation. This could be automated with the help of these commands:
docker run --name forgejo -p 8080:3000 -e FORGEJO__security__INSTALL_LOCK=true -d codeberg.org/forgejo/forgejo:7
$ docker exec forgejo migrate
$ docker exec forgejo forgejo admin user create --admin --username root --password admin1234 --email admin@example.com