cloudserve-infrastructure/roles/forgejo
2025-06-22 11:32:48 +02:00
..
defaults chore(forgejo): Upgrade to LTS v11 2025-06-22 11:32:48 +02:00
files Switch site playbook to use forgejo 2024-06-24 18:30:34 +02:00
handlers Switch site playbook to use forgejo 2024-06-24 18:30:34 +02:00
meta Apply prettier formatting 2024-06-24 20:36:55 +02:00
tasks Apply prettier formatting 2024-06-24 20:36:55 +02:00
templates fix(forgejo): Update to correct woodpecker versions 2025-02-16 21:45:14 +01:00
vars Apply prettier formatting 2024-06-24 20:36:55 +02:00
README.md Apply prettier formatting 2024-06-24 20:36:55 +02:00

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