HebaruSan[m] has joined #spacedock
<
HebaruSan[m]>
If I've understood how all this works, this PR should fill in the last missing piece of the alpha/beta/prod work flow:
<
HebaruSan[m]>
... and of course I send that at 3 AM Deutschland time. Sigh.
Daz has quit [Remote host closed the connection]
Daz has joined #spacedock
HebaruSan[m] has quit [Quit: Idle timeout reached: 10800s]
VITAS[m] has joined #spacedock
<
VITAS[m]>
and on a day when i have to cache a train
<
VITAS[m]>
but ill look at it when im on it
VITAS[m] has quit [Quit: Idle timeout reached: 10800s]
VITAS[m] has joined #spacedock
<
VITAS[m]>
hebarusan merged
VITAS[m] has quit [Quit: Idle timeout reached: 10800s]
Dazzyp has joined #spacedock
Daz has quit [Ping timeout: 202 seconds]
Dazzyp is now known as Daz
HebaruSan[m] has joined #spacedock
<
HebaruSan[m]>
Excellent. Now we just need to generate a secret string and add it to the web hook and config.ini
<
HebaruSan[m]>
The documentation suggests this as an easy way to generate one:
<
HebaruSan[m]>
ruby -rsecurerandom -e 'puts SecureRandom.hex(20)'
<
HebaruSan[m]>
I can take care of config.ini, but I don't have access to the web hook settings
Bart[m] has joined #spacedock
<
Bart[m]>
banishes HebaruSan to a dark oblivion
<
HebaruSan[m]>
Go complain to GitHub, I was just quoting them
<
HebaruSan[m]>
Feel free to spend your time finding the perfect way to generate a random 20-character string
<
Bart[m]>
Feed some random generator into md5_hex()
<
Bart[m]>
(In perl)
<
Bart[m]>
And lob off 12 characters
VITAS[m] has joined #spacedock
<
VITAS[m]>
ill do that in 10h
<
VITAS[m]>
the github part
<
VITAS[m]>
ill take what ever is in the config.ini of sd(insert number please)
<
HebaruSan[m]>
OK, I'll populate the setting for sd2 and sd6 now...
Bart[m] has quit [Quit: Idle timeout reached: 10800s]
VITAS[m] has quit [Quit: Idle timeout reached: 10800s]
HebaruSan[m] has quit [Quit: Idle timeout reached: 10800s]