Skip to content

Commit ea6040b

Browse files
feat: added links
added links to titles
1 parent 989e9b8 commit ea6040b

File tree

1 file changed

+8
-7
lines changed

1 file changed

+8
-7
lines changed

sites/upsun/src/learn/overview/app-life-cycle.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -7,22 +7,23 @@ description: "Understand the {{% vendor/name %}} application lifecycle and learn
77

88
Hooks and web commands let you automate and control different stages of your [application’s lifecycle](#lifecycle-overview).
99

10-
- **Web commands** (`pre_start`, `start`, `post_start`) run **on every instance**, every time that instance starts. They ensure each container is correctly initialised before it receives traffic, including during [horizontal](/manage-resources/adjust-resources.html#horizontal-scaling) autoscaling.
10+
- **[Web commands](/create-apps/app-reference/single-runtime-image.html#web-commands)** (`pre_start`, `start`, `post_start`) run **on every instance**, every time that instance starts. They ensure each container is correctly initialised before it receives traffic, including during [horizontal](/manage-resources/adjust-resources.html#horizontal-scaling) autoscaling.
1111

12-
- **Hooks** (`build`, `deploy`, `post_deploy`) run **once per deployment**, on a single instance. They are used for environment-wide tasks such as preparing the image, running database migrations, or triggering background jobs.
12+
- **[Hooks](/create-apps/hooks/hooks-comparison.html)** (`build`, `deploy`, `post_deploy`) run **once per deployment**, on a single instance. They are used for environment-wide tasks such as preparing the image, running database migrations, or triggering background jobs.
1313

1414
Together, hooks and web commands give you fine-grained control of the application lifecycle, ensuring smooth start-up, reliable [autoscaling](/manage-resources/autoscaling.html), and safe deployments.
1515

1616
## Lifecycle overview
1717

18-
The {{% vendor/name %}} deployment lifecycle has two parallel tracks:
18+
The {{% vendor/name %}} deployment lifecycle has two parallel tracks. Understanding how these two tracks interact helps you choose the right hook for each task:
19+
20+
- **Deployment process** (runs once per deployment)
1921

20-
- Deployment process (runs once per deployment)
2122
This is where your environment is built, deployed, updated, and released.
22-
- Instance startup process (runs on every container instance)
23-
Each new application instance goes through its own startup steps before it can receive traffic.
2423

25-
Understanding how these two tracks interact helps you choose the right hook for each task.
24+
- **Instance startup process** (runs on every container instance)
25+
26+
Each new application instance goes through its own startup steps before it can receive traffic.
2627

2728
### Deployment Lifecycle (Environment-level)
2829

0 commit comments

Comments
 (0)