Environment Start/Stop
This guide is maintained for Ruk-Com PaaS. Screens and options may vary by platform version and account permissions.
Confirm the environment, region and account permissions, and back up current settings before changing a production system.
Among the most common operations for environment management provided by CLI, the start and stop ones can be denoted. Wise usage of these methods can help to significantly cut your spends, especially for development and testing environments (for example, you can stop them for the nighttime, while you are sleeping, and start again at the morning to continue the development).
- In order to stop an environment, that is temporarily non-required, execute the following command (where the highlighted {env_name} placeholder needs to be substituted with the corresponding environment name):
bash Copy
~/jelastic/environment/control/stopenv --envName {env_name}
As you can see, CLI responses with the “result” property equal to 0, meaning that the operation passed successfully and without errors.
1. Later on, you can start your environment with a similar startenv method and make it operable again:
bash Copy
~/jelastic/environment/control/startenv --envName {env_name}
Yes, the environment management is that simple!