Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 17 May 2024 10:16:34 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 278855] www/forgejo 1.21.10.0_1 does not start
Message-ID:  <bug-278855-7788-N4wQUVXsvj@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-278855-7788@https.bugs.freebsd.org/bugzilla/>
References:  <bug-278855-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D278855

--- Comment #5 from Marko Cupa=C4=87 <marko.cupac@mimar.rs> ---
Created attachment 250718
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D250718&action=
=3Dedit
empty dir creation / removal on install / delete

Hi,

indeed, I had set 64 instead of 32 byte string for JWT_SECRET in app.ini, a=
fter
fixing it forgejo started fine, I am already using it.

In the meantime I upgraded to latest 7.0.2, but now my previously valid con=
fig
won't start. Luckily, there's now instruction to check with 'forgejo doctor
check' which I ran and got:

 - [I] Work directory:             "/usr/local/share/forgejo"
 - [E]     Is REQUIRED but is not accessible. ERROR: stat
/usr/local/share/forgejo: no such file or directory

`WORK_PATH =3D /usr/local/share/forgejo` does not exist in app.ini.sample, =
but it
gets added automatically on service start provided git user can write to
app.ini.

I created dir manually and it now starts fine. Interestingly enough, it see=
ms
irrelevant whether git user can write to it (forgejo starts when folder is
root:wheel 755).

What is this dir used for? It seems forgejo works just fine without being a=
ble
to write to it, and it being empty, without also reading from it.

I patched port so that empty dir is created at install (and removed at
deinstall), but perhaps people who understand forgejo internals better can
propose better solution.

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-278855-7788-N4wQUVXsvj>