# Resource groups with sequenced start and stop | ZopNight

> Group resources, attach one schedule, and ZopNight starts them in order: storage, then databases, then compute, then apps, with a delay per resource where you need one.

Source: https://zop.dev/zopnight/resource-groups

---

_Storage, databases, compute, apps_

## Start and stop stacks in order.

Group resources that belong together, attach one schedule to the group, and ZopNight starts them in order: storage first, then databases, then compute, then applications, and stops them in reverse. Set a delay per resource so the database is up before the app server starts.

- 1 — schedule for the whole group
- 4 — start tiers: storage, databases, compute, apps
- 30s — between tiers, plus a delay per resource
- 1 click — starts or stops the whole group

Free to start. No card. The playground just needs your work email.

## Order that holds at 8am.

The stack comes up the way it was built to.

- 01. Group it — Put the resources for one environment or one service together. Each resource belongs to one group, so there is never a question of which schedule wins.
- 02. Attach one schedule — The group's schedule applies to every member, and changing it changes them all.
- 03. Order it — Start runs storage, then databases, then compute, then applications, and stop runs the reverse. Change a resource's tier, or set a start and stop delay per resource.
- 04. Run it from the group — Start or stop the whole group from the group itself, which applies each resource's delay. The tier order runs on the group's schedule, and a bulk start from the inventory skips both.

## Built for the morning start.

Every detail is about coming up in the right order.

- Membership: Exclusive. A resource is in one group with one scheduling source, which rules out two schedules fighting over it.
- Sequencing: Storage, then databases, then compute, then apps on start, the reverse on stop, 30 seconds apart. Change a resource's tier, or add per-resource start and stop delays, when your stack needs something different.
- Budgets and overrides: A group can carry its own budget, shown green, yellow or red, and one group override covers every member at once.
- Before a change: Editing or deleting a group's schedule first shows every member it affects and the monthly cost impact.

## Bring environments up in the right order, every time.

Connect an account, group one environment, and attach a schedule. Ordering is automatic.

[object Object]
