Package Details: gogs 1:0.11.91-1

Git Clone URL: (read-only, click to copy)
Package Base: gogs
Description: Self Hosted Git Service written in Go
Upstream URL:
Keywords: git go gogs
Licenses: MIT
Conflicts: gogs-bin, gogs-dev-git, gogs-git
Submitter: kureikain
Maintainer: Martchus
Last Packager: Martchus
Votes: 54
Popularity: 0.000501
First Submitted: 2014-05-12 08:56
Last Updated: 2020-01-21 14:09

Pinned Comments

Martchus commented on 2017-06-12 22:24

Important note: You likely want to use the official Gitea package instead.

Gitea - a fork of Gogs - has been added to the official repositories:

That means for Arch Linux the decision has been made to support Gitea rather than Gogs. Hence I suggest everyone to use Gitea instead of Gogs for new installations. I've been testing Gitea for a while myself now and it works well. So I'm also going to switch fully to Gitea myself.

Nevertheless I'll continue maintaining this package for a while now to support old installations. However, I'm not doing any fine-tuning for this package anymore.

Further notes
  • If anybody was using the Gitea package from my PKGBUILDs repository: It is easy to migrate the official Gitea package because the packages are structured more or less the same. The only significant difference between the packages is that mine was using the user gitea and the official package the user git. So that has to be changed in the config and for the ownership of /var/lib/gitea.
  • It is also possible to install this Gogs package provided here and Gitea at the same time (of course operating on different databases!). That makes it easy to try out Gitea without breaking the existing Gogs installation. Repos can be copied quite easily using my gogs2gitea script. (I'm afraid migrating isn't possible anymore without installing an old Gitea version first.)
Previous "sticky" note

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 ... Next › Last »

Martchus commented on 2017-10-12 10:11

I'll add it.

yan12125 commented on 2017-10-12 09:47

I have to change AVATAR_UPLOAD_PATH to /var/lib/gogs/data/avatars so that I can upload custom avatars. Mind to add it to 0001-Adjust-config-for-Arch-Linux-package.patch?

Martchus commented on 2017-10-06 14:56

@papush GOGS_CUSTOM is now set to "/var/lib/gogs/custom" in the service file.

papush commented on 2017-10-05 20:55

@Martchus Yes, that seems like the correct way to do it.

Martchus commented on 2017-10-02 17:31

@papush I don't use the custom config path myself. I have just took a look at the Gogs source code myself to find out how the path is computed which suggested the working directory is used. I assumed a function called "WorkDir()" would return the working directory. However, according to Unknown's statement in the issue it doesn't and instead returns the path where the executable is located. So no wonder why the path is "/bin/custom" then.

I still think the custom path should be "/var/lib/gogs/custom" rather than something under "/usr" which is usually used for packaged files only. So I could set GOGS_CUSTOM to "/var/lib/gogs/custom" then?

papush commented on 2017-10-02 16:50

@Martchus There seems to be a bug ( which makes gogs use its executable path as the working directory, and as a result the custom path is set to /bin/custom (even though I launch gogs with the provided .service, which set the PWD to /var/lib/gogs). Am I the only one affected by this ?

Martchus commented on 2017-09-30 18:49

@papush Gogs defaults to "$PWD/custom" for the custom directory. This makes "/var/lib/gogs/custom" for the configuration proposed by this package.

I guess this should be ok. On the other hand, putting custom, unpackages files under /usr/share/... as you propose is quite uncommon.

Note that the config is only not read from "/var/lib/gogs/custom/conf/app.ini" because this has been overridden via CLI argument.

papush commented on 2017-09-30 14:45

You should add GOGS_CUSTOM=/usr/share/gogs/custom to the Environment= line in the systemd service file, as Gogs defaults to /bin/custom for its custom locale/template/theme directory.

Martchus commented on 2017-08-09 19:15

@geekinthesticks I usually build packages in a clean chroot, like the Arch Linux devs build the packages. This is the recommend way to build packages and avoids problems caused by custom system configuration and installed packages.

geekinthesticks commented on 2017-08-09 18:14

My build error is a bit of a mystery! I can build gogs on all the VMs I have tried, except the gogs box. All systems are up to date with the latest packages. I'll do a bit more investigating to see if I can work out why it won't build on my gogs box.