Difference between revisions of "SAC:Gitea"
(Update the info to be up-to-date (Gogs -> Gitea)) |
|||
Line 1: | Line 1: | ||
− | + | Gitea is an '''experimental''' instance of the [https://gitea.io/ Go Git Service] that runs on [[TracsvnVM]] as part of the [[SAC:Git Service|OSGeo Git Services]]. | |
− | It can be accessed via https://git.osgeo.org/ | + | It can be accessed via https://git.osgeo.org/gitea/ (login with your [[SAC:LDAP|OSGeo Userid]]) |
= Files location and configuration = | = Files location and configuration = | ||
− | It is installed in <code>/home/git/ | + | It is installed in <code>/home/git/gitea</code>. |
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 (you need to sign in and be granted access to it, or you'll get a 404). | + | 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 <code>/home/git/ | + | Repositories are in <code>/home/git/gitea-repositories</code> 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 '' | + | 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/ | + | Attachment and session data are in <code>/home/git/gitea/data</code>, with no backup in place at the time of writing. |
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]]) | ||
− | It listens on IP <code>127.0.0.1</code> and TCP port <code> | + | 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 [[TracsvnVM]] for info about the apache configuration. | See [[TracsvnVM]] for info about the apache configuration. | ||
− | + | Gitea is built to be composed by a single binary. | |
− | See https:// | + | See https://gitea.io/ for more info. |
Line 28: | 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]] is willing to help. | ||
== Starting and stopping the service == | == Starting and stopping the service == | ||
− | The service is started via <code>/etc/init.d/ | + | The service is started via <code>/etc/init.d/gitea</code> script which is a symlink to a file under <code>/home/git/gitea/custom/scripts</code> (revision controlled as mentioned above). The init script is symlinked to rc3.d for use in runlevel 3 |
= Client tools = | = Client tools = |
Revision as of 04:01, 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
, 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 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