Differences between revisions 19 and 21 (spanning 2 versions)
Revision 19 as of 2018-09-03 21:56:52
Size: 5003
Comment: adds hints to get it run on stretch using binary installation
Revision 21 as of 2020-01-10 19:02:44
Size: 3359
Editor: ?MichaelLustfield
Comment: Service no longer exists.
Deletions are marked like this. Additions are marked like this.
Line 12: Line 12:
== Install gitea using binay packages from orgin == == Install gitea using binary packages from upstream ==
Line 14: Line 14:
[LANG=DE] For germans you may find help [[https://flobee.cgix.de/gitea-installation-unter-debian-stretch-9/|here]] using the binay installation or just  the install helper [LANG=EN] [[https://github.com/flobee/public/tree/master/shell/gitea|here]]. [LANG=DE] For Germans you may find help [[https://flobee.cgix.de/gitea-installation-unter-debian-stretch-9/|here]] using the binary installation or just the install helper [LANG=EN] [[https://github.com/flobee/public/tree/master/shell/gitea|here]].
Line 19: Line 19:

== Debian's Gitea ==

A Gitea instance for Debian is running at [[https://gitea.debian.net]].

=== Why Gitea? ===

Gitea is fully open source and almost packaged for Debian. It's a breeze to install, but is it enterprise-ready? Integrating well with Debian seems like a good test, doesn't it? :)

=== Service Level ===

This service has been taken off-line and data relocated. Should their be interest in resurrecting it, please contact [[https://db.debian.org/search.cgi?&uid=MTecknology&dosearch=Search|MTecknology]].

=== Authentication ===

Authentication to this service is handled using [[https://sso.debian.org/|Debian's SSO]] service.
Line 61: Line 43:
     -X GET https://gitea.debian.net/api/v1/user      -X GET https://gitea.domain.tld/api/v1/user
Line 68: Line 50:
Navigate to [[https://gitea.debian.net/repo/migrate|/repo/migrate]], fill out the details, click Migrate Repository. Navigate to [[https://gitea.domain.tld/repo/migrate|/repo/migrate]], fill out the details, click Migrate Repository.
Line 81: Line 63:
     -X POST https://gitea.debian.net/api/v1/repos/migrate      -X POST https://gitea.domain.tld/api/v1/repos/migrate
Line 89: Line 71:

=== Maintenance ===

Gitea has these administrator(s):

 * Michael Lustfield (MTecknology)

An up-to-date list can be located on the [[https://gitea.debian.net/org/debian-gitea-svc/teams/owners|Owners page]] of the debian-gitea-svc project.

For simple non-urgent requests, feel free to open an issue against the [[https://gitea.debian.net/debian-gitea-svc/meta-admin/issues|Debian Gitea Service]].

=== To Do ===

 * A [[https://github.com/go-gitea/gitea/issues/2347|feature request]] exists to set the user's email address from Debian's SSO, but it's unlikely to be added any time in the near future.
 * MTecknology's personal mail domain is being used for mail delivery; would be nice to not do that.
 * Need to implement reliable backups that other admins can easily access.

=== Questions ===

 * How are Debian account groups injected or supported? -- Accounts are pulled from SSO. There has been no discussion about groups; they will likely remain manual.

Translation(s): English

Gitea is a git front-end that supports collaborative development, similar to github/gitlab/etc.

Install gitea using binary packages from upstream

[LANG=DE] For Germans you may find help here using the binary installation or just the install helper [LANG=EN] here.

Packaging Process

At this time, gitea is not packaged for Debian. Help is needed to complete existing libjs ITP's blocking the Gitea ITP.

Password Verification

For some actions, gitea requires password verification. In these cases, a password must be configured.

To set a password, navigate to /user/settings/password, click "Forgot password?," and follow the instructions. This will allow you to create a password to acknowledge these prompts.

Package Groups

At this time, package groups are not being created. If you need a group (organization) to exist, please contact an administrator. These groups will be manually created and efforts to contact the package group admins (referenced from alioth) to grant ownership to will be made.


Gitea provides a loosely documented API.

To utilize the API, first log into Gitea and navigate to /user/settings/applications. Use the "Generate New Token" button to generate a key and be sure not to lose it.

Swagger is used to provide a function list underneath /swagger. Two headers will need to be added to API requests: Content-Type and Authorization. Content-Type is simply 'application/json'. Authorization is "token <your_application_token>".

If you were interested in finding your own uid, you would find it with this:

curl -H 'Content-Type: application/json' \
     -H 'Authorization: token 6c0d842e2ed6ac121fb3f2eeac6951ecc2ea' \
     -X GET  https://gitea.domain.tld/api/v1/user

Note: Getting org/team IDs is not currently possible: https://github.com/go-gitea/gitea/issues/1821 (collab-maint=id:2)

To import a project from alioth (using a browser):

Navigate to /repo/migrate, fill out the details, click Migrate Repository.

Note: While it's possible to convert a mirrored (replicated) repo to a cloned one, the reverse is not true.

To import a project from alioth (using the api):


curl -H 'Content-Type: application/json' \
     -H 'Authorization: token 6c0d842e2ed6ac121fb3f2eeac6951ecc2ea' \
     -d "{\"clone_addr\": \"${gitsrc}\", \"uid\": 2, \"repo_name\": \"${gitname}\", \"mirror\": false}" \
     -X POST https://gitea.domain.tld/api/v1/repos/migrate

To instead mirror the repository, use mirror:true instead. The repository will be cloned as a mirror and perform regular checks for new content.

Additional Reading: