An environment's Resources tab moves a service onto a machine of its own, or adds a service or an extra machine, without rebuilding the environment. It does not change a shape in any other way.
What it does
The tab shows the environment's topology, then its machines, then what it runs and where each service came from. Anybody who can see the environment sees that much; the changes below it are for Admins and above.
In production, each service that can move has a choice:
- On the web machine, or
- A machine of its own, with a size for it, from the same provider and region as the rest of the environment. The monthly price is on each size.
A summary shows what will move before anything happens. The new machine is built first; the service follows.
One change at a time. While a machine of the environment is being built, resized or removed, or a database is moving, the tab says so and offers nothing to change. It comes back once the last change has finished. Progress is under Activity.
What can move
| Service | Onto its own machine | Back again |
|---|---|---|
| Cache, search, queue | Yes | Yes; the emptied machine is removed |
| Workers | Yes, once a deploy has recorded some | Yes |
| The database | Only while the environment is still one machine | No |
| Vinyl Cache (Varnish) | No | — |
| The web tier | No | — |
Move the database first. Once the cache or search has moved off, the database option disappears.
Varnish is not offered: it becomes the front door.
Each service gets its own machine. Two moved services cannot share one.
Where it is not offered
- Staging, development and preview environments. Their services are where
vallic.yamlputs them. The one change the tab offers there is an extra machine. For more room, resize their machine. - The dedicated shape, where every service already has its own machine.
- During a free trial, nothing moves onto a machine of its own until the first payment has gone through. Moving a service back onto the web machine still works.
- A shared plan, which has no machines of its own. Moving to a dedicated plan is a migration we do with you: ask support. A service can still be added to the machine it shares.
On the dedicated shape the tab also sets how many web servers and worker machines there are. It does not change the plan.
Adding a service
In production, Add a service offers what the environment does not run yet.
Anywhere else it is Add an extra machine, and offers only that. For staging
or development, name a service in vallic.yaml; the next deploy starts it.
What can be added:
- A service from the catalogue (a cache, a search engine, a queue) of a kind the environment does not run yet. One cache, one search engine: an environment with Redis is not offered Valkey, because that is a swap.
- An extra machine, by its slot name (
pioneer,voyager, …), for the containers your repository describes in.vallic/extra/<slot>.yml. See Extra machines.
Where it runs depends on the environment:
| Environment | A service | An extra |
|---|---|---|
| Production, flexible shape | A machine of its own | A machine of its own |
| Production, dedicated shape | A machine of its own | A machine of its own |
| Staging, development and previews | Through vallic.yaml |
A machine of its own, at full price |
| A shared plan | Through vallic.yaml |
Not offered |
A machine of its own is built in the environment's provider and region, at the size you choose. It is added to the subscription from the day it is built. A summary shows the machine, its size and what it restarts before anything is bought.
The first machine beside one that ran alone restarts it, on a provider that must stop a machine to connect it to a private network (UpCloud). On staging and development that machine is the one they all share, so every environment on it is down for a minute or two. Hetzner connects it without a restart.
A service on the machine that runs the site is not added here: name it in
vallic.yaml, and the next deploy starts it. This is the way to give a service
a machine of its own instead.
Never offered: the database (swapping it is a migration: ask support), Varnish (it becomes the front door), and the web tier. Removing a service is not here either.
What each move costs in downtime
InfluxDB, or a cache that keeps its data: your site shows the offline page while the data crosses, as it does for the database. Until the data has arrived, the site goes on using the old copy, and a machine of its own the service left is given back only once it has. A cache's data crosses in seconds; a large InfluxDB takes longer. Carried off the web machine, the old copy stays there until you remove it under Left behind on the Storage tab (Storage).
A cache that keeps nothing, search or a queue: the service stops while it moves, and its data is not copied. A cache refills on its own. A search index has to be re-indexed by your application. Let a queue drain first: do not count on jobs still sitting in it surviving the move.
The database: your site shows the offline page for the whole copy. A small database is minutes; a large one can be the better part of an hour. Plan it for a quiet time.
The site's address does not change. Nothing you have in DNS needs editing.
What your application needs
Nothing, if it reads its connection details from the environment. The
platform rewrites DB_HOST, REDIS_HOST, SOLR_HOST and the rest to point at
the new machine, over the private network. The credentials and the database name
stay the same.
An application that has localhost or 127.0.0.1 written into its
configuration will lose its database the moment it moves. Check before you
start: see Variables and your framework's page.
The old copy of the database
When the database moves, the copy on the web machine is kept for 72 hours, and then removed. It is not served from. Pointing the site back at it is a support request, not a button.
You can remove it sooner from the Storage tab. If you set the disk split yourself, that tab is also where to reclaim the room it leaves.
Cost
A new machine, moved to or added, is added to the project's subscription at the price shown beside its size, from when it is built. A machine removed by moving a service back comes off it. See Billing for how part-months are charged.
Who can do it
The Admin role, once the project has been built. Support can do it for you too, if you ask. See Teams.
Next
- Machines — resizing, instead of moving
- Extra machines — what runs on an extra
- Shapes — what the layouts are and what each asks of your application
Thank you. Good to know it helped.
Thanks — tell us what was missing. Open a ticket from Support in the console, and we answer on the ticket. Open the console