Package Details: gogs 1:0.13.0-1

Git Clone URL: https://aur.archlinux.org/gogs.git (read-only, click to copy)
Package Base: gogs
Description: Self Hosted Git Service written in Go
Upstream URL: https://gogs.io
Keywords: git go gogs
Licenses: MIT
Submitter: kureikain
Maintainer: krumelmonster
Last Packager: dcelasun
Votes: 50
Popularity: 0.000000
First Submitted: 2014-05-12 08:56 (UTC)
Last Updated: 2023-08-10 14:22 (UTC)

Dependencies (9)

Required by (0)

Sources (3)

Pinned Comments

Martchus commented on 2020-08-24 14:06 (UTC)

The release 0.12.0 will change various configuration variables, e.g. ROOT_URL is changed to EXTERNAL_URL. Please read the official changelog before reporting any issues: https://github.com/gogs/gogs/releases/tag/v0.12.0

Further notes from myself:

  • ROOT_URL did not work at all for me anymore. So it is apparently not just deprecated (as the changelog states).
  • The changelog mentions no alternative to STATIC_ROOT_PATH. It looks like this directory is simply not required at all anymore because files are built into the executable. Overrides should be possible by placing files into the working directory (should be /var/lib/gogs/public with the default config provided by this package; haven't tested yet).

Martchus commented on 2017-06-12 22:24 (UTC) (edited on 2020-08-24 14:22 (UTC) by Martchus)

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

Gitea - a fork of Gogs - has been added to the official repositories: https://www.archlinux.org/packages/community/x86_64/gitea

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.~~~ The official package now uses the user gitea similar to my initial packaging was done.
  • 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.)

Latest Comments

« First ‹ Previous 1 .. 13 14 15 16 17 18

<deleted-account> commented on 2014-09-15 09:06 (UTC)

protake, seems like 'chown -R gogs:gogs /srv/gogs' dont get run.. Try 'sudo chown -R gogs:gogs /srv/gogs' fanningert, I think app.ini.patch should also set 'ROOT = /srv/gogs/repo', and there something wrong with the template thing. It can't find the files in /usr/share/themes/goges/default/public.

sflor commented on 2014-09-15 06:36 (UTC)

After the update I cannot start gogs anymore: start.sh[30817]: 2014/09/15 08:29:33 [setting.go:210 NewConfigContext()] [E] Could not create directory data/attachments: mkdir data: permission denied I'm not sure about the permissions, because where should data/attachments be created exactly?

fanningert commented on 2014-08-02 18:14 (UTC)

Thanks, I updated the packages (gogs, gogs-git, gogs-git-dev). When you have other good hints, say it.

Schmeidenbacher commented on 2014-08-01 08:45 (UTC)

You should consider putting the gogs.service file in /usr/lib/systemd/system/ instead of /etc/systemd/system/. That's where the package provided unit files should go. /etc/systemd/system/ is for the user to put edited unit files for the services in to override the ones in /usr/lib/systemd/system/, if he needs to change something. This allows for cleaner updates to the service file in a package without threatening to overwrite the user's changes.