Differences between revisions 10 and 11
Revision 10 as of 2017-08-21 18:22:06
Size: 3607
Editor: ?MichaelLustfield
Comment:
Revision 11 as of 2017-08-22 21:51:07
Size: 4131
Editor: GuillemJover
Comment: Add some questions
Deletions are marked like this. Additions are marked like this.
Line 80: Line 80:
* https://github.com/gogits/go-gogs-client/wiki/Repositories  * https://github.com/gogits/go-gogs-client/wiki/Repositories
Line 85: Line 85:

=== Questions ===

 
 * How to create new organizations? Do those need to be created manually by an admin? One problem is that the namespaces seem to be shared so there's the danger that they might collide with Debian member accounts created in the future.
 * How are Debian account groups injected or supported?
 * How to contact the admin team? There does not appear to be an admin project nor a contact page?
 * Is the current instance ready for usage or will it be reinstated at some point in the near future?

Translation(s): English

Gitea is a git front-end, similar to github/gitlab/etc.



Packaging Process

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

Additional work need to be merged upstream. Unfortunately, upstream is being a bit stubborn with this one.

Debian's Gitea

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

Hosting is currently provided by MTecknology

Authentication

Authentication to this service is handled using Debian's SSO service.

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.

Note: not currently sending out email; resolution in progress

The API

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.debian.net/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):

gitsrc="https://anonscm.debian.org/git/collab-maint/arduino.git"
gitname="arduino"

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

If it's preferred to keep a repository at it's current location and only import the repository to play with gitea or use a feature it provides, the mirror option can be set.

-d "{\"clone_addr\": \"${gitsrc}\", \"uid\": 2, \"repo_name\": \"${gitname}\" \"mirror\": true}" \

Additional Reading:

To Do

A 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.

Questions

  • How to create new organizations? Do those need to be created manually by an admin? One problem is that the namespaces seem to be shared so there's the danger that they might collide with Debian member accounts created in the future.
  • How are Debian account groups injected or supported?
  • How to contact the admin team? There does not appear to be an admin project nor a contact page?
  • Is the current instance ready for usage or will it be reinstated at some point in the near future?