If you have not yet installed the State Tool, please refer follow the install instructions
Authenticating
You'll need to authenticate to push changes from your CLI or to access your private projects.
Runtime Management
Install and start a runtime from an existing ActiveState project. Don't have a project yet? Create a Project or use the state init command.
Create a new ActiveState Platform project that contains a runtime with the specified language. Run state info language/<language-name> to see all available versions for that language.
This downloads the language interpreter and all required packages to your system. It also adds the activestate.yaml file to your current directory. For more information refer to the checkout documentation.
This runtime will be set as your system default. Run state use reset to unset it.
Your runtime will start in a subshell. Run stop to exit.
Package Management
Packages come from our vetted catalog and are all built on-demand.
Replace <package-name> with the name of the package you want to install.
Import multiple packages using one of the supported file formats.
See a list of matching packages, and their avialable versions, that are in our catalog.
Change Management
You can make changes to your local environment, like adding and removing packages, without affecting the remote project on the Platform and only push them when you're ready.
Update the remote project on the Platform with your local changes.
Bring in the latest changes from the remote project on the Platform.
Running Commands
You can write your own custom scripts and commands and share them as part of your runtime. Learn more about running scripts here.
This runs the hello script, which accepts "world!" as an argument.
Troubleshooting
Stuck? Try these commands or post on our forums.
This shows help for the activate command. You can swap it with any of the other State Tool commands.
If updating fails consistently please uninstall and reinstall State Tool.