Package Details: gogs 1:0.11.34-2

Git Clone URL: (read-only)
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: 49
Popularity: 1.020541
First Submitted: 2014-05-12 08:56
Last Updated: 2018-03-20 20:50

Pinned Comments

Martchus commented on 2017-06-12 22:24

All my packages are managed at GitHub where you can also contribute directly:
Patches are managed under:
There also exist a binary repository:

Latest Comments

Martchus commented on 2018-03-20 20:47

Ok, I'll do when updating anyways.

powerarch commented on 2018-03-20 20:37

This package sees to build just fine on aarch64. Maybe add it to the supported architectures?

Martchus commented on 2018-03-19 22:05

I updated Gogs to use systemd-sysusers in accordance with the official packaging:

This way the install script can be omitted. Hooks will take care of everything instead (even warning about systemctl daemon-reload).

When I upgraded the package on my server, this did not change any existing user/group IDs. So the transition should not cause any trouble.

I also included a script gogs-backup which calls gogs backup using the environment variable and config parameter mentioned in the last comment. It must run as user gogs.

Martchus commented on 2018-02-07 20:58

@drBlaze I haven't tried to restore, but creating a backup is quite easy, eg.:

sudo su gogs
export GOGS_CUSTOM=/var/lib/gogs/custom # the magic line that lets your error go away
gogs backup --config /etc/gogs/app.ini --verbose --target /tmp

drBlaze commented on 2018-02-04 11:26

Has anyone tried to backup & restore? $ gogs backup --config=/etc/gogs/app.ini 2018/02/04 12:02:09 [ INFO] Backup root directory: /tmp/gogs-backup-840218384 2018/02/04 12:02:09 [ INFO] Packing backup files to: gogs-backup 2018/02/04 12:02:09 [FATAL] Fail to include 'custom': open /usr/bin/custom: no such file or directory

Running "systemctl status" confirms Custom path: /usr/bin/custom

This can't be right, right?

davidovitch commented on 2017-12-26 17:15

I had to use an absolute path for the SQLite database file, while the default config setting comes as a relative path. I've added this to the Arch Linux wiki. My installation is running in an Arch linux LXC container, not sure if that makes any difference.

davidovitch commented on 2017-12-23 15:06

@Martchus: thanks! I've updated the Arch Wiki accordingly, maybe a more experienced Gogs user could review the changes I made? For example, I could only see changes taking effect after restarting Gogs (systemctl restart gogs), is that really the case?

I've also tried to use a custom configuration file custom/conf/app.ini (as suggested by the Gogs docs), but I couldn't get that to work using either /usr/share/gogs or /var/lib/gogs as root directory.

Martchus commented on 2017-12-22 20:19

@davidovitch This first-time-configuration via the web UI conflicts with having the config under /etc/gogs indeed. You can decide yourself whether you want to relax the permissions (temporarily) or just edit the config file directly. Note that Gogs only alters this file through the first-time-config. Any other settings are stored in the database.

davidovitch commented on 2017-12-22 20:03

I am a little confused regarding the location of the config file, when finishing off the installation at localhost:3000 (Install steps for first run time) I get:

Fail to save configuration: open /etc/gogs/app.ini.747273564.tmp: permission denied

Martchus commented on 2017-11-24 10:28

Checksums should be fixed now.

All comments