Difference between revisions of "SAC:Gitea"
(Update the info to be up-to-date (Gogs -> Gitea)) |
(→Files location and configuration: data dir is now backed up too) |
||
| Line 13: | Line 13: | ||
Apache running user (''www-data'') is made part of the group to allow for browsing ''gitea-managed'' repositories via existing [[Trac_Instances|trac instances]]. | Apache running user (''www-data'') is made part of the group to allow for browsing ''gitea-managed'' repositories via existing [[Trac_Instances|trac instances]]. | ||
| − | Attachment and session data are in <code>/home/git/gitea/data</code> | + | Attachment and session data are in <code>/home/git/gitea/data</code>. |
It is configured to use [[SAC:LDAP|LDAP]] for authentication and ''PostgreSQL'' as the backend, see the configuration for access parameters. | It is configured to use [[SAC:LDAP|LDAP]] for authentication and ''PostgreSQL'' as the backend, see the configuration for access parameters. | ||
| − | Backups | + | |
| + | Backups are currently automated for the database and data directory via scripts in <code>/osgeo/backup/</code> (start from <code>/osgeo/backup/bacula_before.sh</code>). 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 <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. | ||
| Line 23: | Line 24: | ||
Gitea is built to be composed by a single binary. | Gitea is built to be composed by a single binary. | ||
See https://gitea.io/ for more info. | See https://gitea.io/ for more info. | ||
| − | |||
= Administration = | = Administration = | ||
Revision as of 06:50, 17 December 2017
Gitea 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/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 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). 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 /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 TracsvnVM 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 is willing to help.
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
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