Difference between revisions of "SAC:Gitea"
(→Continuous integration: add Woodie, although non existing yet) |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 7: | Line 7: | ||
It is installed in <code>/home/git/gitea</code>. | It is installed in <code>/home/git/gitea</code>. | ||
| − | Its configuration is in the ''custom/'' subdir and | + | Its configuration is in the ''custom/'' subdir and controlled via ansible. |
| − | |||
Repositories are in <code>/home/git/gitea-repositories</code> and all files are created as readable for any user in the ''git'' group. | Repositories are in <code>/home/git/gitea-repositories</code> and all files are created as readable for any user in the ''git'' group. | ||
| Line 20: | Line 19: | ||
It listens on IP <code>127.0.0.1</code> and TCP port <code>3001</code> via HTTP. Apache is configured to deal with HTTPS and act as a proxy. | It listens on IP <code>127.0.0.1</code> and TCP port <code>3001</code> via HTTP. Apache is configured to deal with HTTPS and act as a proxy. | ||
| − | See [[ | + | See [[TracSVN]] for info about the apache configuration. |
Gitea is built to be composed by a single binary. | Gitea is built to be composed by a single binary. | ||
| Line 29: | Line 28: | ||
At the moment [[User:Strk|Sandro Santilli]] (promoter of the initiative) and Martin Spott have admin privileges from the web UI. | At the moment [[User:Strk|Sandro Santilli]] (promoter of the initiative) and Martin Spott have admin privileges from the web UI. | ||
[[User:Robe|Regina Obe]] and [[Jeff McKenna]] are willing to help. | [[User:Robe|Regina Obe]] and [[Jeff McKenna]] are willing to help. | ||
| + | |||
| + | Server configuration is done via https://git.osgeo.org/gitea/sac/ansible-deployment | ||
| + | (requires login and authorization to see) | ||
== Starting and stopping the service == | == Starting and stopping the service == | ||
| − | The service is | + | The service is managed via systemctl: |
| − | |||
| − | |||
| − | + | - systemctl start gitea | |
| + | - systemctl stop gitea | ||
| + | - systemctl restart gitea | ||
= Continuous integration = | = Continuous integration = | ||
A CI server is associated to the hosting service, | A CI server is associated to the hosting service, | ||
| − | see [[Dronie]] | + | see [[Dronie]] and [[Woodie]] |
[[Category:Infrastructure]] | [[Category:Infrastructure]] | ||
Latest revision as of 07:32, 8 May 2024
Gitea is an instance of the Go Git Service that runs on TracSVN as part of the OSGeo Git Services.
It can be accessed via https://git.osgeo.org/gitea/ (login with your OSGeo Userid)
Files location and configuration
It is installed in /home/git/gitea.
Its configuration is in the custom/ subdir and controlled via ansible.
Repositories are in /home/git/gitea-repositories and all files are created as readable for any user in the git group.
Apache running user (www-data) is made part of the group to allow for browsing gitea-managed repositories via existing trac instances.
Attachment and session data are in /home/git/gitea/data.
It is configured to use LDAP for authentication and PostgreSQL as the backend, see the configuration for access parameters.
Backups are currently automated for the database and data directory via scripts in /osgeo/backup/ (start from /osgeo/backup/bacula_before.sh). No repositories are backed up (what's a distributed code version control system worth otherwise?:). Refer to SAC:Backups for other backup info.
It listens on IP 127.0.0.1 and TCP port 3001 via HTTP. Apache is configured to deal with HTTPS and act as a proxy.
See TracSVN for info about the apache configuration.
Gitea is built to be composed by a single binary. See https://gitea.io/ for more info.
Administration
At the moment Sandro Santilli (promoter of the initiative) and Martin Spott have admin privileges from the web UI. Regina Obe and Jeff McKenna are willing to help.
Server configuration is done via https://git.osgeo.org/gitea/sac/ansible-deployment
(requires login and authorization to see)
Starting and stopping the service
The service is managed via systemctl:
- systemctl start gitea - systemctl stop gitea - systemctl restart gitea
Continuous integration
A CI server is associated to the hosting service, see Dronie and Woodie