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
start_instance(s) and stop_instance(s) add provision job (as run_command and handle_git_command)
start_instance(s)
stop_instance(s)
run_command
handle_git_command
scale_instance and create_release set retired on instances.
scale_instance
create_release
create_instance insert a new instance.
create_instance
I think there is a confusion between two different concepts:
Resistant erosion processes (REP) are setup by the user with the ps command.
ps:scale web=2
ps:scale web=0
ps:stop
ps:restart
The role of an REP is to make sure a dyno is started even if crash happens.
May be useful for #7
The text was updated successfully, but these errors were encountered:
No branches or pull requests
start_instance(s)
andstop_instance(s)
add provision job (asrun_command
andhandle_git_command
)scale_instance
andcreate_release
set retired on instances.create_instance
insert a new instance.I think there is a confusion between two different concepts:
Resistant erosion processes (REP) are setup by the user with the ps command.
ps:scale web=2
, --> create 2 REPps:scale web=0
-> destroy every REP of type webps:stop
--> destroy every REPps:restart
--> do not touch the REP, and restart the dynoThe role of an REP is to make sure a dyno is started even if crash happens.
May be useful for #7
The text was updated successfully, but these errors were encountered: