Creating and sharing a project

Producing a reliable, customized project is a core function of the ActiveState Platform and the following will show you how to create, share, and use projects that include only the languages and artifacts (packages, bundles, patches, etc.) you need for the specific operating system(s) you are working on.

To create your first project:

  1. Sign in to your ActiveState Platform account.
  2. Click the Projects tab to create a personal project, or select an organization from the drop-down to create a project in that organization.
  3. Click the +New Project button.
  4. Select a Language and version for your project.
  5. Choose an operating system(s) from the list provided. Selecting multiple operating systems is restricted to Team Tier and Enterprise Tier accounts.
  6. The project is set to Public by default, if you are a Team Tier or Enterprise Tier member select whether your project will be Public or Private.
  7. A default project name will be given to your project, you can select a unique name for your project (which will act as its default URL).
  8. To finish your build you can click the Finish Creating Project button to move straight to downloading your project. Or you can add packages to your project by:
    • Clicking Search Package Catalog to individually search for and add the packages and versions required for your project. Enter the name of the package or bundle you need and click Add to include them in your project.
    • Clicking Add Dependencies from File to import requirements from a file. For more information on specifying your project requirements using a file, see Creating projects from requirements.txt files.
  9. Clicking Close will bring you back to your Project page with a notice to save your changes. Clicking Save will commit your selection(s) to your project and begin the build process.
  10. Go to the Download Builds tab and copy the text under the “First time install via command line” window and paste it into your command line. If this is an update to an existing project, you can run the state pull command to update your local installation.

Sharing a project

Sharing a project is the simplest way to make sure your development team can get to work and avoid sorting out dependencies or worrying about security/stability issues.

Benefits of sharing a project include:

  • Saving fellow developers time and effort setting up a stable development environment.
  • Accelerate employee onboarding by having the correct, specific dependencies needed for the project immediately available.
  • Educators can standardize student environments and to restrict unneeded artifacts and simplify the learning experience.
  • Organizations can better control which tools developers are using and account for what is being used in the event of patches, updates, or security risks.

To share an existing project:

  1. Once on your Project page, in the Overview tab, click the Install button to generate a “Download and Install” message.
  2. Send the command shown to collaborators (via email, Slack, Microsoft Teams, etc.) to install via their own command line. An example is shown below:
powershell -Command "& $([scriptblock]::Create((New-Object Net.WebClient).DownloadString(''))) -c'state activate --default user-activestate/example_project'"

Using a project created by someone else

After receiving a first time install command to collaborate enter the command into your local command line to access the project.

For Public projects, the command you received will install the project runtime on your machine whether you have the State Tool installed or not. However, without the State Tool, users of that public project cannot configure the project and will be restricted to using the latest version of the build (i.e. the version received).

Users of public projects with the State Tool installed (and who are signed in to the Platform using the state auth command) are able to configure the public project, save any changes, and create new versions that can be shared.

For Private projects (restricted to Team Tier and Enterprise Tier accounts), the recipient must have the State Tool installed and be signed in to the Platform using the state auth command. Users of Private projects who are signed in to the Platform are able to configure the project and view the project’s history using the History tab in the Platform UI.

While in the History tab, previous versions of the project can be accessed by clicking the View to this Commit link, and can be installed by clicking the Revert to this Commit link.