Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 DEFAULT_MAXLIFE_VALUE and DEFAULT_MAXLIFE_UNIT config params #322
base: master
Are you sure you want to change the base?
Add DEFAULT_MAXLIFE_VALUE and DEFAULT_MAXLIFE_UNIT config params #322
Changes from all commits
f00af71
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks much nicer - but the values from bepasty.conf do not get picked up in the web UI.
I'm testing with https://hub.docker.com/r/asmaps/bepasty, editing the code in /usr/local/lib/python3.9/site-packages/bepasty/ if that makes a difference.
Does templates/index.html need some modification, maybe?
<select class="form-control" name="maxlife-unit" size="1">
seems to always pick the first option, which is "Months"...There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, yes, guess it needs to generate different html, making this a bit more complicated...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And that's where my experience ends, unfortunately. Hopefully someone else can chime in.
I'll probably edit index.html in a custom docker image for now...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thinking about whether we could just have a fixed unit (e.g. days) and maybe allow a float value also.
That would be much easier overall, but also require a bigger change in the code and templates. Also, one would need to check the documented api and client code, whether we can do such a change without breaking existing clients.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note:
https://github.com/bepasty/bepasty-client-cli that client uses the existing unit/value web api.