Skip to content
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

Add :ttl configuration option #84

Merged

Conversation

pkarman
Copy link
Contributor

@pkarman pkarman commented Feb 22, 2017

Why: The :expire_after config option controls both the Redis
session expiration and the expiration of the Rails session cookie.
Adding a new config option :ttl allows those controls to be
managed separately.

The most common case would be if you wanted the Rails cookie
to expire when the browser is closed, as it would if :expire_after
were set to nil.

@pkarman pkarman force-pushed the pek-alternate-expiration-config-key branch 4 times, most recently from 02a72cb to bdd1b2b Compare March 1, 2017 21:32
**Why**: The :expire_after config option controls both the Redis
session expiration and the expiration of the Rails session cookie.
Adding a new config option :ttl allows those controls to be
managed separately.

The most common case would be if you wanted the Rails cookie
to expire when the browser is closed, as it would if :expire_after
were set to `nil`.
@monfresh
Copy link

Hello @Jesterovskiy. Is this something you would consider adding to this gem? It looks like there is interest in this feature given that there is another similar PR #85, but we haven't heard anything from the maintainers. Who are the current maintainers?

@Jesterovskiy
Copy link
Collaborator

@monfresh as I understand, this project doesn't have active maintainers now. I get permission for merge and release, because asking about my PR =) So, if you need to merge/release something - you can ask me, but I don't have vision, what features needed or not =(

@pkarman
Copy link
Contributor Author

pkarman commented Aug 8, 2018

@Jesterovskiy afaik, "permission for merge and release" is pretty much the definition of a maintainer. So congratulations! :)

If you have the power to merge this PR and release it, that would be great. @monfresh can confirm but I believe it represents working production code.

The travis failures appear to be rubocop only, afaics. Those should be fixable.

@Jesterovskiy Jesterovskiy merged commit 428b57e into roidrage:master Aug 9, 2018
@monfresh
Copy link

monfresh commented Aug 9, 2018

Yes, I confirm that we are using this code in production from our forked repo. Thanks for merging! Hi @pkarman!

@monfresh
Copy link

@Jesterovskiy Please let me know once you push a new release to rubygems. Thanks!

@Jesterovskiy
Copy link
Collaborator

@monfresh release is done)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants