> ## Documentation Index
> Fetch the complete documentation index at: https://developer.upsun.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Resource initialization
> Learn how resources are allocated by default upon first deployment, and how you can define a resource initialization strategy that better fits your needs.
export const VariableBlock = ({name}) => {
return {name};
};
export const SyncIcon = () => ;
export const MergeIcon = () => ;
export const BranchIcon = () => ;
Resources (CPU, RAM, disk) are allocated per container. Each app and service in your project runs as a separate container within an environment.
By default, when you first deploy your project or add a new container to it,
Upsun uses the `parent` [resource initialization strategy](#specify-a-resource-initialization-strategy),
which copies resource allocations from the parent environment.
If no parent environment exists, Upsun falls back to [preset resource amounts](#default-resources) instead.
You can also specify a different strategy when [branching](#environment-branch), [merging](#environment-merge),
[activating](#environment-activation), or [restoring a backup](#backup-restoration).
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](/docs/manage-resources/adjust-resources#shared-cpu-container-sizes) assigned to each [container type](https://developer.upsun.com/docs/manage-resources/adjust-resources#default-container-profiles) (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](#specify-a-resource-initialization-strategy), or [adjust resources](/docs/manage-resources/adjust-resources) after deployment.
Changing resource allocation directly affects your costs. Review the [Upsun pricing page](https://upsun.com/pricing/) before increasing resources. You can [monitor your current costs](/docs/administration/billing/monitor-billing) 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](#default-resources) instead. |
| `manual` | Skips automatic allocation. The first deployment fails until you configure resources manually through [the Console](https://console.upsun.com/) 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](#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](#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. |
The following table shows the resources Upsun allocates to your containers when you opt for the `minimum` [resource initialization strategy](#specify-a-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](#first-deployment) | `parent`, `default`, `minimum`, `manual` | `parent` |
| [Environment branch](#environment-branch) | `parent`, `default`, `minimum` | `default` (staging) / `minimum` (development), unless a source integration uses its configured strategy |
| [Environment merge](#environment-merge) | `child`, `default`, `minimum`, `manual` | `child` |
| [Environment activation](#environment-activation) | `parent`, `default`, `minimum` | `default` (staging) / `minimum` (development) |
| [Backup restoration](#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](#specify-a-resource-initialization-strategy) Upsun uses to allocate resources
when you first deploy your project or add a new container.
If you're not using a [source integration](/docs/integrations),
you can use a [Git push option](/docs/environments#push-options) to specify a resource initialization strategy.
To do so, run the following command:
```bash Terminal theme={null}
upsun push --resources-init=
```
For example, to use the `minimum` strategy for your deployment, run the following command:
```bash Terminal theme={null}
upsun push --resources-init=minimum
```
Alternatively, you can use the official Git syntax for [push options](/docs/environments#push-options):
```bash Terminal theme={null}
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](/docs/integrations), 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](/docs/integrations/source),
include the `--resources-init` flag in your source integration options.
For example, if you [set up a GitHub integration](/docs/integrations/source/github), use the following options:
```bash Terminal theme={null}
upsun integration:add \
--project \
--type github \
--repository \
--token \
--base-url \
--resources-init
```
#### Update an existing source integration
To specify a resource initialization strategy for an existing source integration,
run the following command:
```bash Terminal theme={null}
upsun integration:update --resources-init=
```
For example, to use the `minimum` strategy for environments created through the integration, run the following command:
```bash Terminal theme={null}
upsun integration:update --resources-init=minimum
```
### Environment branch
Resource initialization strategies
Available: `parent`, `default`, `minimum`
**The default strategy depends on how the environment is created.**
**Without a source integration**, the default strategy depends on the child environment type:
| Environment type | Default strategy | Resources allocated |
| ---------------- | ---------------- | ---------------------------------------------- |
| Staging | `default` | [default resource amounts](#default-resources) |
| Development | `minimum` | [minimum resources](#minimum-resources) |
**With a [source integration](/docs/integrations)**, the `parent` strategy applies by default, unless a different strategy is configured on the integration.
If resource allocation is higher than expected, check the source integration's configured strategy.
To change the strategy used by a source integration, see [Update an existing source integration](#update-an-existing-source-integration).
Use the methods below to specify a different [resource initialization strategy](#specify-a-resource-initialization-strategy).
Regardless of strategy or integration, Upsun automatically 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.
Run the following command:
```bash Terminal theme={null}
upsun environment:branch --resources-init=
```
For example, to inherit resources from the parent environment, run the following command:
```bash Terminal theme={null}
upsun environment:branch --resources-init=parent
```
1. Navigate to the environment you want to branch from.
2. Click **Branch**.
3. Enter a name and a type for the new environment.
4. Select an initialization strategy from the proposed list.
5. Click **Branch**.
### Environment merge
Resource initialization strategies
Available: `child`, `default`, `minimum`, `manual`
Default: `child`
When you [merge](/docs/glossary#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.
Run the following command:
```bash Terminal theme={null}
upsun environment:merge --resources-init=
```
For example, to use the `manual` resource initialization strategy, run the following command:
```bash Terminal theme={null}
upsun environment:merge --resources-init=manual
```
1. Navigate to the environment you want to merge into its parent.
2. Click **Merge**.
3. Select an initialization strategy from the proposed list.
The list of strategies is only displayed if a new app or service is included in the merge.
4. Click **Merge**.
### 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](#default-resources) |
| Development | `minimum` | [minimum resources](#minimum-resources) |
To specify a different strategy, run the following command:
```bash Terminal theme={null}
upsun environment:activate --resources-init=
```
For example, to use the `parent` resource initialization strategy, run the following command:
```bash Terminal theme={null}
upsun environment:activate --resources-init=parent
```
[Setting resources](/docs/manage-resources/adjust-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`
When you [restore a backup](/docs/environments/restore) 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](/docs/environments/restore) 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:
```bash Terminal theme={null}
upsun backup:restore --resources-init=
```
For example, to use the `minimum` resource initialization strategy, run the following command:
```bash Terminal theme={null}
upsun backup:restore --resources-init=minimum
```
When you [restore a backup](/docs/environments/restore) 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](/docs/glossary#sync) means propagating changes from a parent environment into a child environment (the opposite direction of an [environment merge](#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)
When you sync the data, Upsun checks if the child environment's disk size is at least equivalent to the parent's.
If not, the parent environment's disk size is automatically applied to the child environment.
This ensures the sync can succeed.
Run the following commands depending on your needs:
* Sync only resources:
```bash Terminal theme={null}
upsun sync resources
```
* Sync only code:
```bash Terminal theme={null}
upsun sync code
```
* Sync only data:
```bash Terminal theme={null}
upsun sync data
```
* Sync everything:
```bash Terminal theme={null}
upsun sync code data resources
```
You can adjust the command depending on the exact combination of elements you want to sync.
1. Navigate to your Production environment.
2. Click **Sync**.
3. Select the sync options you want from the proposed list.
4. Select **Sync resources from Production into Staging**.
5. Click **Sync**.