Files location and configuration
It is installed in
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/gitea/sac/gitea-config (you need to sign in and be granted access to it, or you'll get a 404). Make sure to use the "gitea" branch.
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
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 TracsvnVM for info about the apache configuration.
Gitea is built to be composed by a single binary. See https://gitea.io/ for more info.
Starting and stopping the service
The service is started via
/etc/init.d/gitea script which is a symlink to a file under
/home/git/gitea/custom/scripts (revision controlled as mentioned above). The init script is symlinked to rc3.d for use in runlevel 3
* Experimental command line interface: https://github.com/andreynering/gogscli
A CI server is associated to the hosting service, although not fully integrated yet. See Drone