Getting Started

1. Go to Granite Control Panel and choose plan.

2. Click on Create app button.

3. Select the Docker image you want to deploy on the NoVPS Cloud Platform. If you are going to deploy a private Docker image, specify the credentials that have read access to the specified image.

4. Select the Docker tag you want to deploy to the platform. You can use the Latest tag if you want to enable automatic updates to your application when the tag is updated in the registry. In addition, you can use an application variable as a tag (the variable name must begin with the $ symbol). This is useful when you create multiple resources from a single Docker image and want to be able to update them simultaneously. For example, you create resources from the novps/test-fastapi image (not actual image) with the tag v1.0.0 and want to be able to update all resources simultaneously to the tag v1.0.1. In this case, you specify $APP_VERSION in the Docker Tag field. Then, create an application variable named APP_VERSION and set its value to v1.0.0. If the variable is not created, the latest tag will be used by default. Now, if you want to roll out another tag, simply replace the value of the APP_VERSION application variable with v1.0.1.

5. In the next step, you will see a list of resources that will be created in the application. If necessary, you can add more resources by clicking the Add more button and repeating the steps for adding a Docker image (steps 3 and 4). Here you can also configure the Docker image for correct startup. To do this, click the Edit button and configure the necessary parameters. You can find a more detailed description of resource parameters in this article.

6. In the next step, you can specify the environment variables that are required to run the container from the Docker image. There are two types of environment variables:

   • Application variables — are passed to all resources within a single application. When application variables are changed, all resources will be updated automatically. You can also specify a variable containing a Docker tag in the application variables, which will allow you to automatically update all resources within the application to the new tag (see step two for more details).
   • Resource variables — are passed only to the containers of the resource for which they are set. If you have created an application variable and a resource variable with the same name, the resource variable will be used.

7. The last step is the final one. Here you can see the future configuration of your application, as well as go to the resource settings if you forgot to specify something. Once you are ready, click the Create button to confirm the creation of the application.

8. Once the application is deployed, you will see a list of running resources and their containers, as well as the statuses of these containers.

The application is now ready to handle the load.