Gitea package names (e.g. OCI images, etc.) can contain `/` charactres. These are encoded as %2F in request paths. Apache needs to forward these sequences to the Gitea server without decoding them. Unfortunately, the `AllowEncodedSlashes` setting, which controls this behavior, is a per-virtualhost setting that is *not* inherited from the main server configuration, and therefore must be explicitly set inside the `VirtualHost` block. This means Gitea needs its own virtual host definition, and cannot rely on the default virtual host.
19 lines
600 B
YAML
19 lines
600 B
YAML
gitea_version: 1.17.1
|
|
gitea_arch: '{{ _gitea_arch_map[ansible_architecture] }}'
|
|
gitea_bin: gitea-{{ gitea_version }}-linux-{{ gitea_arch }}
|
|
gitea_bin_sha256: >-
|
|
{{ _gitea_cksm_map[gitea_version][gitea_arch] }}
|
|
gitea_download_url: >-
|
|
https://dl.gitea.io/gitea/{{ gitea_version }}/{{ gitea_bin }}
|
|
|
|
gitea_ssh_domain: '{{ ansible_fqdn }}'
|
|
gitea_http_domain: '{{ gitea_ssh_domain }}'
|
|
gitea_root_url: 'http://{{ gitea_http_domain }}:3000/'
|
|
gitea_webhook_allowed_host_list:
|
|
- '*'
|
|
|
|
gitea_ssl_certificate: >-
|
|
{{ apache_ssl_certificate }}
|
|
gitea_ssl_certificate_key: >-
|
|
{{ apache_ssl_certificate_key }}
|