ghost-automation/ds_gitea
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 3 Wiki Activity

Minor readme update.

Browse Source
This commit is contained in:
Tom
2026-02-10 12:31:20 +01:00
parent e23f9b1901
commit 9e68459916
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
README.org
View File

@@ -8,13 +8,13 @@ This role installs and configures a [[https://docs.gitea.com/][Gitea]] server.
It uses SQLite as its default database service - with optional PostgreSQL support. It uses SQLite as its default database service - with optional PostgreSQL support.
The role can set up a reverse proxy with SSL. The role can set up a reverse proxy with SSL using Nginx.
- Use the =ds-ufw= role to configure the firewall. - Use the =ds-ufw= role to configure the firewall.
- Use the =ds-posgresql= role to configure the database. - Use the =ds-posgresql= role to configure the database.
- Use the =ds-nginx= role to install the proxy server. - Use the =ds-nginx= role to install the proxy server.
* Role Workflow * Role Behavior
1. Download and install the Gitea binary 1. Download and install the Gitea binary
2. (Optionally) Set up the PostgreSQL user and database 2. (Optionally) Set up the PostgreSQL user and database
@@ -22,8 +22,8 @@ The role can set up a reverse proxy with SSL.
4. Create the required directory structure 4. Create the required directory structure
5. Wait for the secret creation and storage in SOPS - if secrets are not present 5. Wait for the secret creation and storage in SOPS - if secrets are not present
6. Deploy the Gitea configuration 6. Deploy the Gitea configuration
7. Deploy the Gitea systemd service file (With Postgresql support if the backend is used) 7. Deploy the Gitea systemd service file
8. Set up the reverse proxy with optional SSL 8. (Optionally) Set up the reverse proxy with optional SSL
9. Enable and start the service 9. Enable and start the service
* Defaults * Defaults
@@ -80,7 +80,7 @@ gitea_reverse_proxy: ''
* Secrets * Secrets
Always store the production secrets in SOPS, or in Ansible Vault. Always save the production secrets in SOPS, or in Ansible Vault.
Generate the secrets manually when the playbook stops: Generate the secrets manually when the playbook stops: