Let's talk about the different environments that Iterapp offer.

ProdThe environment where the latest working version of your application is installed and made available to end-users. Therefore it must always be in working condition and bug-free
TestThe environment where testing of an application is performed and quality control is done before deploying it to production
Snap(0-9)The environment where developers can test their code in a production-like environment
LocalDevelopers local environment

Your Iterapp application should run in at least two environments:

  • On your local machine (i.e., development).
  • Deployed to the Iterapp platform (i.e., production)

Ideally, your app should run in two additional environments:

  • Snap, for testing deployment and get early feedback before promoting it to Test
  • Test, for deploying the app in a production-like environment. Changes in master will automatically be deployed to Test.

Deploy to an environment

Deploy your app to the environment with

V2✨ V3 ✨

/iterapp deploy <appname> <environment> <branch>.

/iterapp deploy <appname> <environment> <branch>.

The iterapp.toml-file has a property, default_environment, which is set to test by default.

This means that the branch that is set to default in the github repository, most likely master or main, will be auto-deployed to test whenever a merge to master with a successful build is done.


V2✨ V3 ✨

See how to deploy with slack for detailed information.

See CLI for detailed information.

V2✨ V3 ✨

Verify your app is up and running in the desired environment. A link to the environment should be seen in the #iterapp-logs slack group.

Verify your app is up and running in the desired environment. The url of the environment is something like https://<environment>.<appname>.app.iterate.no.