Record which repos are using the webhook

[groovecoder]

No description provided.

[Faeranne]

Going to use this issue as an excuse to properly learn postgres

[groovecoder]

Don't let postgres turn into a yak-hole though. We can look for something easier if we want.

[Faeranne]

In case it starts to, what alternatives would you suggest?

[groovecoder]

Even finding a way to use Heroku logs would work for me. Or adding New Relic, or anything really. Surely something in https://addons.heroku.com/?q=analytics or https://addons.heroku.com/?q=metrics should work. 😄

[Faeranne]

Don't we already log the payload? That would have the repo name in it.

[groovecoder]

Log it where? 😄 I'm happy to close this if I can already see the payloads/repos somewhere.

[Faeranne]

my bad. it got removed in the great console.log purge of #25
I'll add it back.

[openjck]

Fixed with #39.

[openjck]

My mistake. We have #40 open for restoring this.

[openjck]

We still need to add persistent logs. I can look into that tomorrow.

[Faeranne]

I believe we are using something like papertrail, which just uses heroku's logs to save them.

[Faeranne]

Refer to @groovecoder's last comment on #40 for more details.

[openjck]

I added the "Fixa" Papertrail plan. That gives us 50MB of logging per day, 365 days of logs, and searching up to 7 days in the past. The more expensive plans just increase the data cap; the other values stay the same.

Fixa for Blixa!