[Bug 238230] www/gitea 1.8.1 missing conf file causes failure in start

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238230

--- Comment #5 from stb at lassitu.de ---
Unfortunately, Gitea does not really use a "standard" file layout for config
files, messages catalogs, templates, etc., but expects them to live right next
to the executable binary.

In the FreeBSD port, I'm installing the files in the places that a FreeBSD user
would expect them to live ($PREFIX/etc, $PREFIX/share, ...).

The start script will run gitea with appropriate command line arguments to
direct it to the correct location of these files. That means that running gitea
without any such command line arguments will fail.

Also note that running gitea as root will likely mess up permissions, as gitea
expects to run as (and be able to modify files as) the git user.

The start script uses daemon(8) to write the output of the gitea process to
syslog as daemon:debug. Either configure syslog to write debug output to a
file, or set gitea_facility and gitea_priority in rc.conf to values that make
messages show up in an existing log file.

For example, setting gitea_priority=error and (re-)starting the gitea service
should make those messages appear in /var/log/messages.

Also note that when upgrading from an earlier release to Gitea 1.8.x, you need
to add a new config option, or set permissions on the config file so gitea can
add the option itself. See pkg-message for details.

-- 
You are receiving this mail because:
You are the assignee for the bug.