Configuration parameters

Detailed description of resource configuration parameters

You can configure resources during the addition process, as well as on the Settings tab for already created resources.

﻿

Some parameters are only available for existing resources. When you change the parameters, the resource will be automatically redeployed. If your application has multiple resources, only the one whose parameters you changed will be updated. The others will continue to work as usual.

•Name — this is the name of the resource that will be displayed in the resource list. It is used only for the convenience of distinguishing between resources.

•Type — use this field to define the behavior of the Docker image:

•web-app— the Docker image will have its own public domain, through which it will be accessible on the global Internet. For correct operation, you must specify an HTTP port that can accept requests and return responses.

•worker — use this type for background tasks or for  that must always be running.For example, this could be an event queue handler or a private API that should not be publicly accessible but will be used by other resources within the application (Internal Ports must be configured for correct operation)

•cron-job — this is a scheduled task that must be run on a specific schedule. It is not accessible via http/tcp publicly or within the application. It only runs at the scheduled time; the container is not used at other times.

•Replicas — this setting allows you to select the configuration of containers that will be launched: CPU, RAM, as well as the number of these containers.

Please note that cron-jobs do not allow you to specify the number of containers launched, as it is assumed that this is always a single instance.The available configurations also depend on the pricing plan:

•only the lower configurations are available in the Starter plan

•Professional allows you to choose more powerful settings

•Business and Enterprise plans offer all configurations without restrictions.

•Command — here you can specify the command that will be used as the entrypoint in the container. You can use one Docker image with different commands to run different resources, such as HTTP API, worker, and cron jobs.

•HTTP Port (web-app only) — specify the HTTP port that will receive and process HTTP requests.

•Internal Ports (web-app and worker) — additional ports that will be available for connection within the application (for example, for communication between resources via internal DNS).

•Schedule (cron-job only) allows you to specify the schedule according to which the container should be launched. Use standard cron syntax. You can learn more about it here.

•Allow overlapping? determines the behavior of scheduled container launches.

•If Forbid mode is selected, a new container will not be launched until the previous one has finished running, even if it is time for it to launch.

•If Allow mode is selected, you are allowing multiple containers to launch concurrently.

﻿

Read also

About Resources

Explaining resources in NoVPS Cloud Platform