Using Log Level Debug shows too many redis connections about vapor-auth-template HOT 3 CLOSED

I am not sure if this is something I want to add to the template. It's a configuration issue, so it's up to the user to actually configure the refresh interval and the respective logging levels. I think we should leave it as is, and let the user decide whether to change it or not.

Also, this issue only occurs when you run the queues worker in process with your main Vapor application. Which is not recommended in production. So you can just comment out the startInProccessWorkers() call when debugging your application or alternatively changing the refresh interval.

from vapor-auth-template.

My opinion is there is absolutely nothing that indicates to someone that they need to configure the refresh interval.
Considering its sending emails and that is part of the templates advertised functionality it should do something other then thrash redis multiple times per second

Perhaps an assertion that it has been configured.
Or ar least mention of it in the docs.
Especially for the purpose of email verification 2 mins is a good balance of fast response with thrashing redis.

from vapor-auth-template.

I do wonder how the refresh interval would behave at scale. That could be a reason to poll faster.

from vapor-auth-template.