From: sineemore <sineemore@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: gitea: fix INSTALL script
Date: Mon, 20 Apr 2020 00:13:20 +0200 [thread overview]
Message-ID: <20200419221320.6jkzbFkY4VTIqAXxZwu51oLCJvqC4YKCn5Rm4RNWPNo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18705@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]
New comment by sineemore on void-packages repository
https://github.com/void-linux/void-packages/pull/18705#issuecomment-616233544
Comment:
@sgn
The command
```
sed -i "s!<SECRET_KEY>!$secret!" etc/gitea.conf
```
should change the line
```
SECRET_KEY = !#@FDEWREWR&*(
```
in /etc/gitea.conf.
As you can see, sed pattern will fail.
So right now we already have broken code in INSTALL script.
___
Code, that generates gitea new SECRET_KEY during web based installation: https://github.com/go-gitea/gitea/blob/ad1b6d439fe0e0875e54227e0bc23a74411f490e/routers/install.go#L345
Also there is a way to generate new SECRET_KEY with gitea binary itself:
https://github.com/go-gitea/gitea/blob/37c3db7be6dd6fc5ee085979cc5f5dda09d978c3/docs/content/doc/usage/command-line.en-us.md#generate
next prev parent reply other threads:[~2020-04-19 22:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 0:27 [PR PATCH] " voidlinux-github
2020-02-02 19:09 ` voidlinux-github
2020-02-23 23:41 ` Piraty
2020-02-24 15:25 ` sineemore
2020-02-24 15:32 ` sineemore
2020-04-19 14:43 ` sgn
2020-04-19 22:12 ` sineemore
2020-04-19 22:13 ` sineemore [this message]
2020-04-19 22:15 ` sineemore
2020-04-19 22:16 ` sineemore
2020-04-19 22:21 ` [PR PATCH] [Updated] " sineemore
2020-04-19 22:25 ` sineemore
2020-04-19 22:30 ` sineemore
2020-04-20 0:06 ` [PR PATCH] [Merged]: " the-maldridge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200419221320.6jkzbFkY4VTIqAXxZwu51oLCJvqC4YKCn5Rm4RNWPNo@z \
--to=sineemore@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).