Date: Fri, 27 Oct 2017 19:09:10 +0200 From: Stefan Bethke <stb@lassitu.de> To: FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: Upgrading www/gitea to 1.2.0 Message-ID: <4219FD84-FE4C-4C93-8662-867751AAA849@lassitu.de> In-Reply-To: <1A7EBCD8-30AF-490A-B552-F84DAA30C93C@lassitu.de> References: <1A7EBCD8-30AF-490A-B552-F84DAA30C93C@lassitu.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_957FAFEC-9969-413C-A18E-0BD4BFCBCA2E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Am 15.10.2017 um 09:52 schrieb Stefan Bethke <stb@lassitu.de>: >=20 > If you=E2=80=99r using the Gitea port, the update to 1.2.0 will = require you to add a new INTERNAL_TOKEN key to the security section. See = /usr/local/etc/gitea/conf/app.ini.sample for details. Gitea will not = start until this key is added to the configuration. >=20 > Gitea will try to add this key itself, but will fail if the app.ini = file is not writable by the gitea user, which is the default after = installation. Since a couple of people have run into this problem, here=E2=80=99s a = bit more info: Gitea has no daemon mode itself, so the port is using daemon(8) to run = gitea as a daemon. Also, gitea writes a lot of stuff to stdout while = it=E2=80=99s running, even when you have configured logging through = app.ini. Up to and including version 1.2.1 of the port, stdout and = stderr are thrown away by daemon(8). If gitea fails to start up using the port (i. e. you=E2=80=99re running = 'service gitea start=E2=80=98 and it=E2=80=99s not running afterwards), = and there=E2=80=99s no log output in /var/log/gitea, you need to start = it in the foreground. You can use this command line: # /usr/bin/env -i 'GITEA_WORK_DIR=3D/usr/local/share/gitea' = 'GITEA_CUSTOM=3D/usr/local/etc/gitea' 'HOME=3D/usr/local/git' = 'PATH=3D/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin' = 'USER=3Dgit' /usr/local/sbin/gitea web (as a single line) This should produce error messages. If the error message says that = Gitea cannot write the config file, it is trying to add variables to the = config file; the only known instance so far is the new INTERNAL_TOKEN = variable. Either allow Gitea to write the config file, or use = app.ini.sample as a guide on where to add the INTERNAL_TOKEN variable, = and how to produce the token value. I=E2=80=99ve just submitted port version 1.2.2 to Bugzilla (#223283). = The rc script there will log Giteas output to syslog. In a default = configuration, the output should show up in /var/log/debug.log. HTH, Stefan -- Stefan Bethke <stb@lassitu.de> Fon +49 151 14070811 --Apple-Mail=_957FAFEC-9969-413C-A18E-0BD4BFCBCA2E Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEzBAEBCgAdFiEEJ+hF98o4r3eU/HiPD885WK4W4sEFAlnzaDYACgkQD885WK4W 4sH9zQf+P4Eno9eK/xZgdj4wL0Og/3xQ8GFIoZqNG0x5k1uWH5VkN7m4ir8RDy+Q PVKgnxw/SoKZpT47QAD6zJJYZuGex3JJwMM7kQSZzl3ytrTy+UwB9yBXt9kuZfA/ ru+SqkoJcINlmGKOT3v4DiEe2gbwkZTK1PtnlIANFu6sCII4i8LSzjXdZ85KIeG3 ipY4m1ANF5Wbl+cDqO41sY1sdMyPOgjhSva7rEOaO5z0zf1prrDGLUvbMzyx0D/5 +BTEsfiLjPPED8As62bSqWGrHKBogdZXJ/OQFhPfZVxyTiYL+Z9NUSAAQJfjiuqY w0ZXCNWBbdWmr0s8l/8GqlgfFVJlvQ== =XXpn -----END PGP SIGNATURE----- --Apple-Mail=_957FAFEC-9969-413C-A18E-0BD4BFCBCA2E--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4219FD84-FE4C-4C93-8662-867751AAA849>