The Servers page shows where your services run and how they're spread. The machines themselves are Alf's to look after: how much CPU, memory and disk each has left isn't shown, only whether a server takes new services right now.
Each server is a dot on the map and a card below it: its region, whether it's online, and how many of your services run there. A server that only your organization runs on is marked Only yours (see private servers).
One row per service:
A service that's on no server at all shows No server yet; it's placed as soon as one can take it.
Alf keeps room on every server on purpose: sleeping services need somewhere to wake up, and when a server fails, its services need somewhere to go. So a server whose CPU or memory use stays above a limit takes no new services until its load is down again. Everything already on it keeps running, wakes, scales and can be redeployed as usual.
What you see:
409 with the code servers_full). Nothing is created.What helps: choose another region or Anywhere under Scaling → Regions, or try again a little later. If it keeps happening, tell us at contact@runalf.com: more servers are our job.
Servers tidy up after themselves, so nothing has to be run by hand:
| What goes | How often |
|---|---|
| Containers a finished command left behind | every 10 minutes |
| Images nothing refers to any more (what a rebuild leaves) | hourly |
| Build cache older than a week | nightly |
| Images of a service that moved to another server | nightly, once it's been gone a day |
A disk over 85% full doesn't wait for the night: everything runs at once.
Two things are never touched. Volumes are your data, and go only when you delete the volume or the service. A sleeping service's container is kept, because that's what it wakes from — it looks stopped, but it isn't rubbish.
Container logs are capped at three files of 50 MB, so one noisy app can't fill a server. Older lines are dropped; send what you want to keep somewhere else.