On 03/16, Florian Obser wrote: > On Sat, Mar 16, 2019 at 03:30:09PM +0300, Pavel Korovin wrote: > > I'm thinking of several workarounds for existing setups: > > > > 1. Leave default config in the new location /etc/gitea/app.ini and > > create a symlink to the old config location: > > # cd /etc/gitea && rm app.ini && ln -s conf/app.ini app.ini > > > > 2. Leave default config in the new location and overrride it in > > /etc/rc.conf.local: > > gitea_flags="web -c /etc/gitea/conf/app.ini" > > > > 3. Change default config to the old location /etc/gitea/conf/app.ini > > in Gitea's rc script: > > daemon_flags="web -c /etc/gitea/conf/app.ini" > > > > Suggestions? > > I'm over the bump now, and the list from my first mail was exhaustive > for my setup. Things change and stuff breaks, maybe just extend the > description in current.html so that we have a better discription for > the 6.5 upgrade notes? OK, what about something like the updated gitea entry in faq/current.html:
--- Gitea default configuration file location changed from /etc/gitea/conf/app.ini to /etc/gitea/app.ini. GITEA_CUSTOM directory location has changed from /etc/gitea to /var/gitea/custom. Gitea's ROOT_PATH for logs has changed from /var/gitea/log to /var/log/gitea. Since Gitea hardcodes path to confguration file in ssh configuration and hooks, in order to keep _existing_ setup working, instruct Gitea to use the old configuration file location by adding the following to /etc/rc.conf.local: gitea_flags="web -c /etc/gitea/conf/app.ini" change the ROOT_PATH location in [log] section of /etc/gitea/conf/app.ini: [log] ROOT_PATH = /var/log/gitea and move custom files from /etc/gitea to /var/gitea/custom, if any. Later you can update the ssh config and hooks and remove gitea_flags from /etc/rc.conf.local. --- Please advise. -- With best regards, Pavel Korovin
