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
#26 allowed to skip the concurrent setup lock, but the default behavior should be not to lock the setup at all.
Let's use an optional ON_CONTAINER_PREVENT_CONCURRENT_SETUP environment variable that prevents the concurrent setup instead.
ON_CONTAINER_PREVENT_CONCURRENT_SETUP
Also, let's rename the on_setup_lock_acquired method with to_setup_container so the development entrypoint scripts look like this:
on_setup_lock_acquired
to_setup_container
require 'on_container/dev/rails' set_given_or_default_command if command_requires_setup? to_setup_container do # Stuff to setup the container... end end
The text was updated successfully, but these errors were encountered:
No branches or pull requests
#26 allowed to skip the concurrent setup lock, but the default behavior should be not to lock the setup at all.
Let's use an optional
ON_CONTAINER_PREVENT_CONCURRENT_SETUP
environment variable that prevents the concurrent setup instead.Also, let's rename the
on_setup_lock_acquired
method withto_setup_container
so the development entrypoint scripts look like this:The text was updated successfully, but these errors were encountered: