Resource initialization

Resources (CPU, RAM, disk) are allocated per container. Each app and service in your project runs as a separate container within an environment.

This page describes resource initialization on Upsun Flex projects. On Upsun Fixed projects, resources are automatically distributed across your containers, and you cannot configure per-container resources manually. For details, see container sizes in the Upsun Fixed documentation.

By default, when you first deploy your project or add a new container to it, Upsun uses the parent resource initialization strategy, which copies resource allocations from the parent environment. If no parent environment exists, Upsun falls back to preset resource amounts instead. You can also specify a different strategy when branching, merging, activating, or restoring a backup. The strategy applied by default depends on how the environment is created:

For standard branching and activation, the default strategy depends on the environment type.
For environments created through a source integration, the strategy configured on the integration applies instead.

Default resources

Upsun allocates the following default resources to every container when deployed for the first time:

Resource type	Default amount
CPU	0.5
RAM	Depends on the container profile assigned to each container type (for example, PHP uses `HIGH_CPU`).
Disk size*	512 MB

* Only applicable if the app or service requires a disk (for example, databases such as MariaDB or PostgreSQL). To allocate different resources, specify a resource initialization strategy, or adjust resources after deployment.

Changing resource allocation directly affects your costs. Review the Upsun pricing page before increasing resources. You can monitor your current costs in the Console.

Specify a resource initialization strategy

Upsun provides the following resource initialization strategies:

Strategy	Description
`default`	Uses the parent environment’s resource allocation for new containers. If no parent environment exists, allocates default resources instead.
`manual`	Skips automatic allocation. The first deployment fails until you configure resources manually through the Console or `resources:set` in the CLI. This strategy lets you set the exact resources you want with a single deployment. Other strategies may require fine-tuning after the first deployment, which generates a second deployment. During that window, your environment runs briefly with unnecessary resources, and both deployments cause downtime.
`minimum`	Uses the Upsun minimum resources for new containers.
`parent`	Uses the parent environment’s resource allocation for new containers. If no parent environment exists, or if the container does not exist on the parent environment, falls back to allocating default resources.
`child`	Uses the child environment’s resource allocation for new containers. Used only when merging a child environment into its parent.
`backup`	When restoring a backup, initializes new containers using the same resource allocation as when the backup was taken.

Minimum resource amounts per container type

The following table shows the resources Upsun allocates to your containers when you opt for the minimum resource initialization strategy.

Container	CPU	RAM	Disk*
.NET core	0.1	64 MB	0 MB
Chrome Headless	0.1	64 MB	None
Elasticsearch	0.1	448 MB	256 MB
Elasticsearch Premium	0.1	448 MB	256 MB
Elixir	0.1	64 MB	0 MB
Go	0.1	64 MB	0 MB
InfluxDB	0.1	448 MB	256 MB
Java	0.1	448 MB	0 MB
Kafka	0.1	448 MB	512 MB
MariaDB	0.1	448 MB	256 MB
Memcached	0.1	352 MB	None
MongoDB	0.1	448 MB	256 MB
MongoDB Premium	0.1	448 MB	256 MB
Network Storage	0.1	448 MB	256 MB
Node.js	0.1	64 MB	0 MB
OpenSearch	0.1	448 MB	256 MB
Oracle MySQL	0.1	448 MB	256 MB
PHP	0.1	64 MB	0 MB
PostgreSQL	0.1	448 MB	256 MB
Python	0.1	64 MB	0 MB
RabbitMQ	0.1	448 MB	256 MB
Redis ephemeral	0.1	352 MB	None
Redis persistent	0.1	352 MB	256 MB
Ruby	0.1	64 MB	0 MB
Rust	0.1	64 MB	0 MB
Solr	0.1	448 MB	256 MB
Varnish	0.1	448 MB	None
Vault KMS	0.1	448 MB	256 MB

* The disk size is set to None when the container never uses disk, and to 0 MB when the container doesn’t require disk but can use it.

You can specify a resource initialization strategy when performing the following actions:

Action	Available strategies	Default
First deployment	`parent`, `default`, `minimum`, `manual`	`parent`
Environment branch	`parent`, `default`, `minimum`	`default` (staging) / `minimum` (development), unless a source integration uses its configured strategy
Environment merge	`child`, `default`, `minimum`, `manual`	`child`
Environment activation	`parent`, `default`, `minimum`	`default` (staging) / `minimum` (development)
Backup restoration	`backup`, `parent`, `default`, `minimum`	`backup`

First deployment

Resource initialization strategies

Available: parent, default, minimum, manual
Default: parent

You can define which resource initialization strategy Upsun uses to allocate resources when you first deploy your project or add a new container.

Without a source integration
With a source integration

If you’re not using a source integration, you can use a Git push option to specify a resource initialization strategy. To do so, run the following command:

Terminal

upsun push --resources-init=<INITIALIZATION_STRATEGY>

For example, to use the minimum strategy for your deployment, run the following command:

Terminal

upsun push --resources-init=minimum

Alternatively, you can use the official Git syntax for push options:

Terminal

git push upsun -o resources.init=minimum

You can specify a different resource initialization strategy for each deployment.

If you’re using a source integration, you can specify a resource initialization strategy for that integration.

After a resource initialization strategy is specified for a source integration, it applies to environments created through that integration until you change it.This behavior can differ from the environment-type defaults described for standard branching, which may result in larger resources being allocated than expected.

When creating a new source integration

To specify a resource initialization strategy when creating your source integration, include the --resources-init flag in your source integration options.
For example, if you set up a GitHub integration, use the following options:

Terminal

upsun integration:add \
  --project <PROJECT_ID> \
  --type github \
  --repository <OWNER/REPOSITORY> \
  --token <GITHUB_ACCESS_TOKEN> \
  --base-url <GITHUB_URL> \
  --resources-init <INITIALIZATION_STRATEGY>

Update an existing source integration

To specify a resource initialization strategy for an existing source integration, run the following command:

Terminal

upsun integration:update --resources-init=<INITIALIZATION_STRATEGY>

For example, to use the minimum strategy for environments created through the integration, run the following command:

Terminal

upsun integration:update --resources-init=minimum

Environment branch

Resource initialization strategies

Available: parent, default, minimum
Default: default (staging) / minimum (development)When using a source integration, defaults are per environment type:

default for production and staging environments
minimum for development environments

parent is not available for production environments in source integrations.

Environment type	Default strategy	Resources allocated
Staging	`default`	default resource amounts
Development	`minimum`	minimum resources

To override these defaults, use the CLI (development environments only) or the API (all environment types). See the With a source integration tab below.

Use the methods below to specify a different resource initialization strategy.

Regardless of strategy or integration, Upsun applies the parent’s disk size to the child environment if the child’s disk size is smaller. This ensures the branch can be created.

Without a source integration
In the Console (without source integration)
With a source integration

Run the following command:

Terminal

upsun environment:branch --resources-init=<INITIALIZATION_STRATEGY>

For example, to inherit resources from the parent environment, run the following command:

Terminal

upsun environment:branch --resources-init=parent

When you push a new branch to your repository, your source integration creates an environment using the resource initialization strategy configured on the integration.To override these defaults:

Using the CLI (development environments only)

Run the following command to update your integration’s resource initialization strategy:

Terminal

upsun integration:update --resources-init=<INITIALIZATION_STRATEGY>

For example, to use the parent strategy:

Terminal

upsun integration:update --resources-init=parent

When using the CLI, the value applies to development environments only. Production and staging environments always use the default strategy.

Using the API (full per-type control)

To set the resource initialization strategy independently for each environment type, use the API:

Terminal

curl -X PATCH https://api.upsun.com/projects/<PROJECT_ID>/integrations/<INTEGRATION_ID> \
  -H "Authorization: Bearer <API_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{
    "environment_init_resources": {
      "production": "<STRATEGY>",
      "staging": "<STRATEGY>",
      "development": "<STRATEGY>"
    }
  }'

Valid strategies: minimum, default, manual, parent (however, parent is not available for production environments).See available resource initialization strategies for details.

Environment merge

Resource initialization strategies

Available: child, default, minimum, manual
Default: child

When you merge a child environment into its parent, any apps and services that exist on the child but not on the parent are created on the parent environment. These new apps and services are granted resources according to the selected strategy. However, you can specify a different resource initialization strategy.

Apps and services already running on the parent environment keep their existing resources.

Using the CLI
In the Console

Run the following command:

Terminal

upsun environment:merge --resources-init=<INITIALIZATION_STRATEGY>

For example, to use the manual resource initialization strategy, run the following command:

Terminal

upsun environment:merge --resources-init=manual

Environment activation

Resource initialization strategies

Available: parent, default, minimum
Default: default if the new environment is of type staging, minimum if the new environment is of type development

When you activate a new environment, the resource initialization strategy applied depends on the environment type:

Environment type	Default strategy	Resources allocated
Staging	`default`	default resource amounts
Development	`minimum`	minimum resources

To specify a different strategy, run the following command:

Terminal

upsun environment:activate --resources-init=<INITIALIZATION_STRATEGY>

For example, to use the parent resource initialization strategy, run the following command:

Terminal

upsun environment:activate --resources-init=parent

Setting resources on an inactive environment using the Console or the CLI automatically activates it.

Backup restoration

Resource initialization strategies

Available: backup, parent, default, minimum
Default: backup

Using the CLI
In the Console

When you restore a backup using the CLI, you can restore it to your current environment or a different environment.

Restore to your current environment

By default, when you restore a backup using the CLI, it is restored to your current environment. The resources of every container running on the environment revert to the state they were in when the backup was taken.

To skip restoring resources, use the --no-resources option.

If you deleted containers after backing up but before restoring, they are recreated using the backup strategy and granted the same resources as when the backup was taken.

To skip restoring deleted containers, use the --no-code option.

When you restore previously deleted containers, you can specify a different resource initialization strategy for them.

Restore to a different environment

The backup strategy applies by default. All apps and services are initialized as new containers on the environment, and granted the same resources as in the backup. You can specify a different resource initialization strategy for all containers.

Specify a resource initialization strategy

Run the following command:

Terminal

upsun backup:restore --resources-init=<INITIALIZATION_STRATEGY>

For example, to use the minimum resource initialization strategy, run the following command:

Terminal

upsun backup:restore --resources-init=minimum

When you restore a backup using the Console, it is restored to your current environment. The resources of every container running on the environment revert to the state they were in when the backup was taken.

To skip restoring resources, use the --no-resources option.

If you deleted containers after backing up but before restoring, they are recreated using the backup strategy and granted the same resources as when the backup was taken.

To skip restoring deleted containers, restore the backup using the CLI and use the --no-code option.

Environment sync

Syncing an environment means propagating changes from a parent environment into a child environment (the opposite direction of an environment merge). You can sync:

Only the code
Only the data (databases, files)
Only the resources (CPU and RAM, instances, and disk space)
Any combination of the three (code and data, code and resources, data and resources, or all three)

If the child’s disk is smaller than the parent’s, Upsun automatically applies the parent’s disk size before syncing. This ensures the sync can succeed.

Using the CLI
In the Console

Run the following commands depending on your needs:

Sync only resources:
Terminal
upsun sync resources
Sync only code:
Terminal
upsun sync code
Sync only data:
Terminal
upsun sync data
Sync everything:
Terminal
upsun sync code data resources
You can adjust the command depending on the exact combination of elements you want to sync.

Get Started

Core Concepts

Configure Apps & Services

Build, Deploy & Run

Manage Projects

Manage Environments

Manage Resources

Observability & Metrics

Integrations

Troubleshooting

Resources

Default resources

Specify a resource initialization strategy

First deployment

Resource initialization strategies

When creating a new source integration

Update an existing source integration

Environment branch

Resource initialization strategies

Using the CLI (development environments only)

Using the API (full per-type control)

Environment merge

Resource initialization strategies

Environment activation

Resource initialization strategies

Backup restoration

Resource initialization strategies

Restore to your current environment

Restore to a different environment

Specify a resource initialization strategy

Environment sync

​Default resources

​Specify a resource initialization strategy

​First deployment

Resource initialization strategies

​When creating a new source integration

​Update an existing source integration

​Environment branch

Resource initialization strategies

​Using the CLI (development environments only)

​Using the API (full per-type control)

​Environment merge

Resource initialization strategies

​Environment activation

Resource initialization strategies

​Backup restoration

Resource initialization strategies

​Restore to your current environment

​Restore to a different environment

​Specify a resource initialization strategy

​Environment sync

Default resources

Specify a resource initialization strategy

First deployment

When creating a new source integration

Update an existing source integration

Environment branch

Using the CLI (development environments only)

Using the API (full per-type control)

Environment merge

Environment activation

Backup restoration

Restore to your current environment

Restore to a different environment

Specify a resource initialization strategy

Environment sync