pygospa

Activity Graph

Page 1 of 1

2017-10-27

[15:12:48] pygospa: Remote host closed the connection

2017-10-25

[01:22:08] pygospa: Ping timeout: 255 seconds
[01:23:46] pygospa: has joined #ruby

2017-10-10

[14:48:33] pygospa: Ping timeout: 248 seconds
[14:50:29] pygospa: has joined #ruby
[16:15:29] pygospa: Ping timeout: 248 seconds
[16:17:32] pygospa: has joined #ruby
[21:22:16] pygospa: Ping timeout: 255 seconds
[21:24:14] pygospa: has joined #ruby

2017-10-08

[14:49:35] pygospa: Ping timeout: 240 seconds
[14:51:35] pygospa: has joined #ruby

2017-08-30

[09:27:29] pygospa: Remote host closed the connection

2017-08-12

[18:02:09] pygospa: Ping timeout: 258 seconds
[18:03:46] pygospa: has joined #ruby

2017-08-07

[07:44:20] pygospa: has joined #ruby

2017-08-05

[08:36:31] pygospa: Quit: leaving
[08:36:51] pygospa: has joined #ruby
[09:56:38] pygospa: Quit: leaving
[09:57:01] pygospa: has joined #ruby
[14:39:55] pygospa: Quit: Lost terminal

2017-08-04

[08:03:32] pygospa: has joined #ruby

2015-12-06

[00:11:58] pygospa: Ping timeout: 260 seconds
[00:28:51] pygospa: has joined #ruby
[00:37:30] pygospa: Ping timeout: 246 seconds

2015-12-05

[22:28:59] pygospa: has joined #ruby

2015-11-22

[03:38:36] pygospa: Ping timeout: 264 seconds

2015-11-21

[02:18:53] pygospa: Disconnected by services
[02:19:01] pygospa: has joined #ruby

2015-11-11

[03:19:23] pygospa: Ping timeout: 252 seconds
[04:42:38] pygospa: has joined #ruby

2015-11-01

[20:06:48] pygospa: has joined #ruby

2015-10-25

[19:38:16] pygospa: Quit: leaving
[19:39:00] pygospa: has joined #ruby
[20:03:57] pygospa: Quit: reboot tut gut
[20:04:15] pygospa: has joined #ruby
[20:51:34] pygospa: Remote host closed the connection

2015-10-23

[10:03:22] pygospa: has joined #ruby

2015-10-18

[04:57:43] pygospa: Disconnected by services

2015-10-16

[00:20:25] pygospa: has joined #ruby

2015-10-15

[23:34:20] pygospa: Ping timeout: 265 seconds
[23:35:55] pygospa: has joined #ruby

2015-10-14

[00:21:15] pygospa: Ping timeout: 260 seconds
[00:32:53] pygospa: has joined #ruby
[03:43:11] pygospa: Ping timeout: 240 seconds
[03:44:24] pygospa: has joined #ruby
[16:50:14] pygospa: *.net *.split
[16:59:55] pygospa: has joined #ruby
[17:07:17] pygospa: *.net *.split
[17:10:26] pygospa: has joined #ruby

2015-09-18

[01:48:45] pygospa: Ping timeout: 252 seconds
[02:10:42] pygospa: has joined #ruby

2015-07-30

[08:38:10] pygospa: Ping timeout: 252 seconds
[09:45:43] pygospa: has joined #ruby

2015-07-16

[01:45:25] pygospa: Ping timeout: 255 seconds
[01:45:45] pygospa: has joined #ruby

2015-07-14

[00:40:47] pygospa: Ping timeout: 264 seconds
[00:47:47] pygospa: has joined #ruby

2015-06-20

[01:32:46] pygospa: Remote host closed the connection
[01:38:21] pygospa: has joined #ruby

2015-06-17

[00:46:37] pygospa: Ping timeout: 264 seconds
[00:48:13] pygospa: has joined #ruby
[00:55:07] pygospa: Ping timeout: 264 seconds
[00:56:38] pygospa: has joined #ruby

2015-06-07

[21:45:21] pygospa: Quit: "Restart with new irssi config"
[21:46:56] pygospa: has joined #ruby

2015-06-06

[23:05:10] pygospa: Quit: leaving
[23:14:48] pygospa: has joined #ruby

2015-06-01

[10:43:30] pygospa: has joined #ruby

2014-05-13

[18:21:19] pygospa: Hi! I've got a question regarding secrets.yml. I am fairly new to rails, I did help in a project once (learning by doing) and I've worked through the Railstutorial online book - so this question might be dumb ;) My question is as follows: How does rails in production know how to set the secret_key_base? Because in the secrets.yml it's just read from ENV, so as of my understanding the rails server must somehow generate a key, musn't i
[18:21:20] pygospa: Now if it does, this must be a reproducable step, which renders the secret key base useless. If it doesn't what exactly happens? Having a new key every time would render old cookies useless... Do I have to manually insert it into env, every time the server restarts?