What problem does this solve?
When a user submits the correct flag for a challenge with a running instance, the instance continues running until it is manually stopped or times out. This can leave unnecessary instances running and consume resources even though the challenge has already been solved.
Proposed solution
Add a configurable deployment option such as auto-stop-on-submit: true/false.
When enabled, rCTF should automatically stop the user's running challenge instance after a correct flag submission. When disabled, the existing behavior remains unchanged and the instance continues running normally.
This should be configurable per deployment so operators can choose the behavior that fits their setup.
Workarounds or alternatives
Currently, users or administrators need to manually stop the instance after solving the challenge, or wait for the instance to expire based on its configured timeout.
What problem does this solve?
When a user submits the correct flag for a challenge with a running instance, the instance continues running until it is manually stopped or times out. This can leave unnecessary instances running and consume resources even though the challenge has already been solved.
Proposed solution
Add a configurable deployment option such as auto-stop-on-submit: true/false.
When enabled, rCTF should automatically stop the user's running challenge instance after a correct flag submission. When disabled, the existing behavior remains unchanged and the instance continues running normally.
This should be configurable per deployment so operators can choose the behavior that fits their setup.
Workarounds or alternatives
Currently, users or administrators need to manually stop the instance after solving the challenge, or wait for the instance to expire based on its configured timeout.