-
Notifications
You must be signed in to change notification settings - Fork 32
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
Feature Request [Force Expiration] #54
Comments
+1 on that one! |
Sounds reasonable, will definitely look into that ASAP. Question is if that should be yet another environment variable or if I should bite into the sour apple and allow configuration via a file. |
Well I mean, having the freedom to completely decide what expiration-options one would like to have, would indeed be a beautiful addition. If you take the Challenge, I imagine to see the various options like: enum ExpirationValue {
Bool(bool),
Int(u32),
}
struct ExpirationConfig {
after_read: bool,
never: bool,
minutes: ExpirationValue,
days: ExpirationValue,
weeks: ExpirationValue,
years: ExpirationValue,
} If ExpirationValue is set to false; the Option is just "not present" in the UI. If set to an integer it's "that value". aaanyway: What ever path you might choose, thanks for your quick reply on that topic mate! 🥇 |
To bikeshed a tiny bit here: i usually am fine with just having stuff like this as an environment, as most service managers (systemd, docker, etc) allow loading .env files. On the other hand a core issue is that env vars do not lend themselves well to multiple values and some custom format has to be invented and documented (even if its just |
Before i open a new feature request for something that actually lured me here, i like to confirm the scope of the work done on this feature request as we might overlap. I was looking for a way to a) freely config the expiration for each individual item, like @denissteinhorst mentioned above, or b) a way to statically configure the expirations a bit more to my liking (example: add in case something like this is already part of the works related to this request, i can spare the extra feature request, otherwise i would be happy to open a new one specifically for this topic. On topic and for what it's worth: |
When setting the environment variable |
Hey folks,
Is it possible to add a flag that removes the never expires option so one either has to pick an expiration time (maybe max also controllable) or burn after read?
Many thanks in advance
The text was updated successfully, but these errors were encountered: