Warning: file_exists(): open_basedir restriction in effect. File(/srv/http/vhosts/aur.archlinux.org/public/web/locale//en/LC_MESSAGES/aurweb.mo) is not within the allowed path(s): (/srv/http/vhosts/aur-dev.archlinux.org/:/etc/aurweb/) in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/streams.php on line 90
AUR (en) - gitea

Notice: Undefined variable: name in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/pkgfuncs.inc.php on line 248

Package Details: gitea 1.0.1-3

Git Clone URL: https://aur-dev.archlinux.org/gitea.git (read-only)
Package Base: gitea
Description: Git with a cup of tea, forked from Gogs. Is a Self Hosted Git Service in the Go Programming Language.
Upstream URL: http://gitea.io
Licenses: MIT
Conflicts: gitea-git, gitea-git-dev
Submitter: frederik
Maintainer: frederik
Last Packager: frederik
Votes: 7
Popularity: 3.483750
First Submitted: 2016-11-28 17:05
Last Updated: 2017-01-27 01:40

Dependencies (7)

Required by (0)

Sources (4)

Pinned Comments

frederik commented on 2017-01-23 17:12

To use gitea with openssh OOTB you may want to change the home directory of the git user to /var/lib/gitea/repos:

usermod -d /var/lib/gitea/repos git

Latest Comments

1 2 Next › Last »

robertgzr commented on 2017-01-25 23:34

This also works on armv6/7h using https://hastebin.com/ulakadugep.bash

frederik commented on 2017-01-23 18:21

@BMRMorph
Thanks for your input. I hope I find a better solution soon :)

BMRMorph commented on 2017-01-23 18:13

Woho...it was not my indention to begin such an discussion.
This where only my thoughts in the direction "user experience".
If the package did that what you want it to do then it's fine :)

BUT...in my eyes the "usermod" hint isn't the right way.
Maybe you can ensure that it doesn't harm your system, an i can too...but for all others??? This command definitely changes the settings of the extra/git package and did you know which other package of the 10 thousands rely on the fact that the git users HOME is "/"...?
But as i said...no offence, just my 2 cent ;)

frederik commented on 2017-01-23 17:12

To use gitea with openssh OOTB you may want to change the home directory of the git user to /var/lib/gitea/repos:

usermod -d /var/lib/gitea/repos git

frederik commented on 2017-01-23 17:10

@fbis251 I agree. Will provide a quick description here an in the install script. Thx

fbis251 commented on 2017-01-23 17:08

@frederik At the very minimum mention that using openssh + gitea won't work out of the box and add some instructions on how to change the home directory so that sshd can properly find the authorized_keys file gitea is using for authentication

Note that having to do a special setup using openssh with gitea's authorized_keys file isn't in gitea's documentation and it isn't readily apparent to people installing this package from the AUR

EDIT

Honestly I find the gogs approach of adding a package-specific system user may be cleaner in the long run instead of messing with the git system user's home directory

frederik commented on 2017-01-23 17:02

Do you need a quick guide how to keep things running or is it about the choice of the user?

BTW: You SHOULD adapt your gogs.service to make sure gogs starts after your DB. If you want to run things OOTB without worrying about anything you may be interested in docker...

fbis251 commented on 2017-01-23 16:39

@frederik

Like @BMRMorph, I had to mess with the git system user's home directory to get gittea + openssh access to work at all.

Right now if someone installs gogs, they can use gogs@server after setting up their ssh keys in the options.

The same cannot be said about gitea. If you install gitea, set up an ssh key in the options and attempt to pull/push to a repo using ssh you will be prompted for a password for the git@server user

Again, working with the gogs package, not with the gitea package

frederik commented on 2017-01-23 16:28

@BMRMorph
> I understand you, but in this case the package isn't working out of the box with ssh access.
You wrote "integrated ssh could be used" -> it works ootb

> Changing the git users home changes effectively the settings of another package (git) so i can not say for sure if this doesn't break another app.
You should be fully aware of your system. If you are not, feel free to use a different user for gitea.

> The integrated ssh could be used, yes, but then you can not use port 22 (or any other privileged port) with the git user.
You may use a different port.

> As the gogs Package creates an own user i think gitea should also run as an other user.
"useradd gitea..." feel free :)

BMRMorph commented on 2017-01-23 16:07

@frederik: I understand you, but in this case the package isn't working out of the box with ssh access.
Changing the git users home changes effectively the settings of another package (git) so i can not say for sure if this doesn't break another app.
The integrated ssh could be used, yes, but then you can not use port 22 (or any other privileged port) with the git user.
As the gogs Package creates an own user (also gitolite) i think gitea should also run as an other user. Don't understand me wrong, maybe the fault is the git package with the "/" home dir ;) but i don't think that this is going to change.