[OSGeo] #3084: deploy Gitea via ansible

#3084: deploy Gitea via ansible
----------------------------+----------------------------------------
Reporter: strk | Owner: strk
     Type: task | Status: new
Priority: normal | Milestone: Sysadmin Contract 2024-III
Component: SysAdmin/Gitea | Keywords:
----------------------------+----------------------------------------
We need an easier way to deploy gitea config changes to staging
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/3084&gt;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

#3084: deploy Gitea via ansible
----------------------------+-----------------------------------------
Reporter: strk | Owner: strk
     Type: task | Status: new
Priority: normal | Milestone: Sysadmin Contract 2024-III
Component: SysAdmin/Gitea | Resolution:
Keywords: |
----------------------------+-----------------------------------------
Comment (by strk):

This is currently blocked by the password store of osgeo being in unusable
state due to expired public key. Ref: sac - OSGeo Git Services: Gitea - Git with a cup of tea
/password-store/issues/4
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/3084#comment:1&gt;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

#3084: deploy Gitea via ansible
----------------------------+-----------------------------------------
Reporter: strk | Owner: strk
     Type: task | Status: new
Priority: normal | Milestone: Sysadmin Contract 2024-III
Component: SysAdmin/Gitea | Resolution:
Keywords: |
----------------------------+-----------------------------------------
Comment (by strk):

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: GitHub - s-hamann/ansible-gitea: Ansible role to install and configure Gitea

With that code I successfully deployed staging gitea from ansible (only
the config file and templates, not the binary)
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/3084#comment:2&gt;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

#3084: deploy Gitea via ansible
----------------------------+-----------------------------------------
Reporter: strk | Owner: strk
     Type: task | Status: new
Priority: normal | Milestone: Sysadmin Contract 2024-III
Component: SysAdmin/Gitea | Resolution:
Keywords: |
----------------------------+-----------------------------------------
Comment (by strk):

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
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/3084#comment:3&gt;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

#3084: deploy Gitea via ansible
----------------------------+-----------------------------------------
Reporter: strk | Owner: strk
     Type: task | Status: closed
Priority: normal | Milestone: Sysadmin Contract 2024-III
Component: SysAdmin/Gitea | Resolution: fixed
Keywords: |
----------------------------+-----------------------------------------
Changes (by strk):

* status: new => closed
* resolution: => fixed

Comment:

Wiki updated: SAC:Gitea - OSGeo
gitea-config repo archived.

Considering this tiket closed.
--
Ticket URL: <#3084 (deploy Gitea via ansible) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.