#3084 closed task (fixed)
deploy Gitea via ansible
| Reported by: | strk | Owned by: | strk |
|---|---|---|---|
| Priority: | normal | Milestone: | Sysadmin Contract 2024-III (strk) |
| Component: | SysAdmin/Gitea | Keywords: | |
| Cc: |
Description
We need an easier way to deploy gitea config changes to staging
Change History (5)
comment:1 by , 6 months ago
comment:2 by , 6 months ago
Some secrets currently found in the app.ini file are not really required to be kept somewhere for the long run, specifically the JWT secret (completely unused) and the internal secret. I'm not sure those are good to store in the password store.
From an Ansible role I then borrowed code to read secrets from an existing config, if any: https://github.com/s-hamann/ansible-gitea
With that code I successfully deployed staging gitea from ansible (only the config file and templates, not the binary)
comment:3 by , 6 months ago
I've now also deployed production via ansible. Will update wiki and make the https://git.osgeo.org/gitea/sac/gitea-config repository read only for future removal
comment:4 by , 6 months ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Wiki updated: https://wiki.osgeo.org/wiki/SAC:Gitea gitea-config repo archived.
Considering this tiket closed.
comment:5 by , 5 months ago
| Milestone: | Sysadmin Contract 2024-III → Sysadmin Contract 2024-III (strk) |
|---|
Milestone renamed
This is currently blocked by the password store of osgeo being in unusable state due to expired public key. Ref: https://git.osgeo.org/gitea/sac/password-store/issues/4