Know what needs to run
List the processes your application requires. An HTTP service handles requests, a worker processes background jobs, and a scheduled task runs at a particular time. Give each one a clear start command. Choose a supported runtime version and record it with the project.
Separate files from durable data
Build output can be recreated; uploaded files and database records usually cannot. Decide which data must survive a restart before deploying. Keep temporary files disposable and place persistent data in storage with an explicit backup policy. Test restoration, not just backup creation.
Check behavior, not just a process
A running process can still be unusable. Check an ordinary page, a representative request and its important dependencies. Use bounded timeouts. After a release, compare failure patterns with the previous version and keep a rollback procedure that includes configuration compatibility.