Marty Oehme
b6f7934c5f
In addition to the connected forgejo instance, we can now also target a remote gitea instance for woodpecker agents, should we want to.
34 lines
1,006 B
YAML
34 lines
1,006 B
YAML
---
|
|
forgejo_version: 7
|
|
|
|
forgejo_upstream_file_dir: "{{ docker_stack_files_dir }}/{{ stack_name }}"
|
|
|
|
forgejo_use_https: true
|
|
|
|
# the subdomain link forgejo will be reachable under
|
|
subdomain_alias: git
|
|
subdomain_ci_alias: ci
|
|
|
|
forgejo_db_database: forgejo
|
|
forgejo_db_username: forgejo
|
|
forgejo_db_password: forgejo
|
|
|
|
forgejo_app_admin_username: Myforgejousername # can not be set to admin in Forgejo
|
|
forgejo_app_admin_password: Myforgejopassword
|
|
forgejo_app_admin_email: myadmin@mydomain.mytld
|
|
|
|
# forgejo_smtp_host: domain.com:port
|
|
# forgejo_smtp_username: my@username.com
|
|
# forgejo_smtp_password: <password>
|
|
# forgejo_smtp_force_tls: false # forces tls if it is on a non-traditional tls port. Overwrites starttls so should generally be off
|
|
|
|
forgejo_use_ci: false
|
|
# forgejo_ci_github_client:
|
|
# forgejo_ci_github_secret:
|
|
# forgejo_ci_gitlab_client:
|
|
# forgejo_ci_gitlab_secret:
|
|
# forgejo_ci_forgejo_client:
|
|
# forgejo_ci_forgejo_secret:
|
|
# forgejo_ci_gitea_url:
|
|
# forgejo_ci_gitea_client:
|
|
# forgejo_ci_gitea_secret:
|