rykloud envs
Environments: ask, approve, stop, restore, update, destroy, watch
An environment is a place your project runs: production, staging, a developer's own. Asking for one plans it and prices it; an owner of the organisation approves exactly that price before anything starts at the cloud. Stopping keeps its data and costs nothing at the cloud; restoring brings it back as it was.
Also: env, environments, environment
Commands
- rykloud envs listEnvironments of the organisation
- rykloud envs getAn environment: its state, plan and price, addresses, versions and timeline
- rykloud envs createAsk for an environment: it is planned and priced, then approved by an owner
- rykloud envs optionsSizes, places and products you may ask for, with prices
- rykloud envs approveApprove an environment's plan at its price (owners)
- rykloud envs stopStop it and keep its data; nothing runs or bills at the cloud
- rykloud envs restoreStart a stopped environment from its kept data
- rykloud envs retryTry a failed step again
- rykloud envs cancelCancel an environment that has not started
- rykloud envs wakeWake a stopped environment (any member)
- rykloud envs destroyDestroy an environment and everything in it
- rykloud envs watchFollow an environment's progress until it settles
- rykloud envs versionsWhat it runs, what it could run, and the update on its way
- rykloud envs updateReview an update: planned and priced, then approved by an owner
- rykloud envs logsThe logs of what runs in an environment
- rykloud envs backupBack up the environment now (or --test a restore of the latest backup)
Every command also takes the global flags.