-
Notifications
You must be signed in to change notification settings - Fork 128
How to deal with comments #23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I like the idea of logging in using Github. I am wondering if using Cloudflare or so wouldn't help with preventing bots. Clouflare seems to prevent "attacks"... |
I think it's fine to require Github OAuth login (#21) since 99% of people looking to use ActiveAdmin are going to have a Github account. We just need to make sure not to:
|
@seanlinsley you mean "not in the repo" right? If yes, I agree with you |
Yes, it was a list of things not to do with double negations. :) On Sat Jan 17 2015 at 3:36:21 AM Timo Schilling notifications@github.com
|
Sorry, I didn't read the not in "We just need to make sure not to:" |
I'm closing this, there is still the #21 |
I think the timeouts come from to much comments in the database.
Since now we have a Heroku scheduler wich deletes the comments each hour.
I have following the logs during the first scheduler run, before it starts we have 99% timeouts, ~1 minute after the run the timeouts going down to 0%.
There are 3 way to go for the future:
My opinions are:
I'm interested in, what others think about this? // cc: @seanlinsley, @pcreux, @eshaiju
The text was updated successfully, but these errors were encountered: