SAC:Gitea
Gogs is an experimental instance of the Go Git Service that runs on TracsvnVM as part of the OSGeo Git Services.
It can be accessed via https://git.osgeo.org/gogs/ (login with your OSGeo Userid)
Files location and configuration
It is installed in /home/git/gogs.
Its configuration is in the custom/ subdir and revision-controlled under git.
A clone of the configuration git repo can be accessed here: https://git.osgeo.org/gogs/sac/gogs-config (you need to sign in and be granted access to it, or you'll get a 404).
Repositories are in /home/git/gogs-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 gogs-managed repositories via existing trac instances.
Attachment and session data are in /home/git/gogs/data, with no backup in place at the time of writing.
It is configured to use LDAP for authentication and PostgreSQL as the backend, see the configuration for access parameters. Backups should be currently automated for the database (but at the time of writing there are no details in SAC:Backups)
It listens on IP 127.0.0.1 and TCP port 3000 via HTTP. Apache is configured to deal with HTTPS and act as a proxy.
See TracsvnVM for info about the apache configuration.
Gogs is composed by a single binary and a bunch of templates and web assets (images, javascript). See https://gogs.io/ for more info.
Administration
At the moment Sandro Santilli (promoter of the initiative) and Martin Spott have admin privileges from the web UI.
Starting and stopping the service
The service is started via /etc/init.d/gogs script which is a symlink to a file under /home/git/gogs/custom/scripts (revision controlled as mentioned above). The init script is symlinked to rc3.d for use in runlevel 3
Client tools
* Experimental command line interface: https://github.com/andreynering/gogscli
Continuous integration
A CI server is associated to the hosting service, although not fully integrated yet. See SAC:Drone