GHOSTVPS / Automation
Launch a preinstalled WordPress or Docker VPS safely
Choose the right preinstalled image, verify the application, publish it behind HTTPS and set an update and backup routine.
Updated · GhostVPS

Before you start
A plan and location where the selected application image is actually available. Preinstalled images differ by plan, version and provider; confirm the exact Console choices before ordering. Have a domain and a place for independent backups if the service will be public.
Choose the image that matches the workload
Use WordPress when the goal is a site with an existing CMS; use Docker when you need to run and maintain your own containers. Compare the actual plan resources and image choices in Console. Do not assume every location supports both images, or that an image includes a managed application service.

Confirm what the image installed
After delivery, read the service notes and log in through the documented route. For WordPress, identify the site URL, admin account and PHP/database versions. For Docker, check the engine and Compose plugin before deploying a project. Change default credentials immediately if any were supplied.
Your VPS · Linux terminal
docker version
docker compose version

Restrict access before exposing a new app
Keep management ports private or limited to trusted addresses. For Docker, inspect published ports with docker ps; a container bound to 0.0.0.0 may be reachable publicly. For WordPress, use a strong unique administrator password and update core, themes and plugins from trusted sources.
Your VPS · Linux terminal
docker ps --format "table {{.Names}}\t{{.Ports}}"
Connect the domain and confirm HTTPS
Point the chosen hostname to the correct service, configure the web server or reverse proxy and issue a certificate using the supported workflow. Visit the public hostname over HTTPS and verify the displayed application is yours. Do not expose a development service merely because a DNS record now points to the VPS.
Back up and test an update path
For WordPress, back up both files and database; for Docker, include configuration, volumes and any database data. Restore a small test item before relying on the backup. Document how you will update the application and roll back, then check logs after the first public request.



