Difference between revisions of "SAC:Gitea"
| Line 8: | Line 8: | ||
It is installed in ''/home/git/gogs''. | It is installed in ''/home/git/gogs''. | ||
Its configuration is in the ''custom/'' subdir and revision-controlled under git. | 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 ( | + | 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. | 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|trac instances]]. | + | Apache running user (''www-data'') is made part of the group to allow for browsing ''gogs-managed'' repositories via existing [[Trac_Instances|trac instances]]. |
| − | 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 should be currently automated for the database (but at the time of writing there are no details in [[SAC:Backups]]) | Backups should be currently automated for the database (but at the time of writing there are no details in [[SAC:Backups]]) | ||
| Line 21: | Line 21: | ||
Gogs is composed by a single binary and a bunch of templates and web assets (images, javascript). | Gogs is composed by a single binary and a bunch of templates and web assets (images, javascript). | ||
See https://gogs.io/ for more info. | See https://gogs.io/ for more info. | ||
| + | |||
| + | The service is started via upstart <code>/etc/init.d/gogs</code> which is a symlink under <code>/home/git/gogs/custom</code> (revision-controlled as mentioned above). | ||
= Starting and stopping the service = | = Starting and stopping the service = | ||
Revision as of 23:25, 20 April 2016
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.
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.
The service is started via upstart /etc/init.d/gogs which is a symlink under /home/git/gogs/custom (revision-controlled as mentioned above).
Starting and stopping the service
The service is started via sysV init script /etc/init.d/gogs which is a symlink to a file in /home/git/gogs/scripts. The init script is symlinked to rc3.d for use in runlevel 3
Administration
At the moment Sandro Santilli (promoter of the initiative) and Martin Spott have admin privileges from the web UI.