Before connecting a server, build an accurate picture of what you own and what it already runs. DOCKOCK readiness observations help inform this review.
Confirm that you are authorized to manage the VPS. Verify its host fingerprint through a trusted provider console or another independent channel. Keep an access recovery method outside the application you are evaluating.
Record services, listening ports, domains and persistent data. Unknown infrastructure should be preserved until its role is understood. Do not approve a plan that replaces something you cannot identify.
Check the supported operating system, available CPU, memory and disk space. Allow headroom for the operating system and stateful services. A build can need different resources from the final application runtime.
Write down the expected connection state and application behavior. Identify who will investigate a failure and how access will be recovered. Continue to the deployment-plan guide only after connection and readiness issues are understood.
Ownership, identity, capacity, and the workloads already on your server.
Read the guideFollow your source through services, storage, routing, and verification.
Read the guideUnderstand what it takes to recover application code and persistent data.
Read the guideLet’s talk about your stack.
This conversation is closed.
