We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
docker/runauth.sh This seems kind of messy.
Perhaps have gasket catch the signals. and another flag for the base config stuff (starting fresh or not).
In fact whether we start fresh or not should be decided by the user. so add an option for that (passing env variables in docker??)
how would docker restart mode work then - if wanted to keep the current rules after a crash?
The text was updated successfully, but these errors were encountered:
re restart mode: change dockerfile.auth to use ENTRYPOINT then in docker run ... <put argument here> or in docker-compose 'command' see https://stackoverflow.com/a/41968585 and https://stackoverflow.com/a/40312311
A) if base-acls.yaml use that (this is the latest) if not use base-acls.yaml-orig (the original nothing authed).
B) always use base-acls.yaml-orig
C) always use base-acls.yaml
Sorry, something went wrong.
No branches or pull requests
docker/runauth.sh This seems kind of messy.
Perhaps have gasket catch the signals. and another flag for the base config stuff (starting fresh or not).
In fact whether we start fresh or not should be decided by the user. so add an option for that (passing env variables in docker??)
how would docker restart mode work then - if wanted to keep the current rules after a crash?
The text was updated successfully, but these errors were encountered: