{
  "id": 16865804,
  "title": "Docker Deploy Without a DevOps Engineer: Dockerfile to Live HTTPS in 6 Steps (2026)",
  "url": "https://urgent.news/2026/10/28/docker-deploy-without-a-devops-engineer-dockerfile-to-live-https-in-6",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-28T07:34:52.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/vishvajeetshukla/docker-deploy-without-a-devops-engineer-dockerfile-to-live-https-in-6-steps-2026-lfk"
  },
  "original_language": "en",
  "account": "Running Docker containers on a VPS without a full DevOps team is doable. The key is getting the container onto a real server, behind a domain, with HTTPS and a way to rollback updates. This guide shows how to do all of that in six steps. Docker on a VPS is useful for any language - Python, Go, Rust, PHP, Ruby, Java and .NET apps all run the same once they are in a container. The image you test is the image you run, for consistency.\n\nFirst, properly install Docker and Compose on Ubuntu using Docker's official repository or convenience script. Then, clone the repository, build the Docker images with a tag based on the commit hash, and configure the container to listen on localhost port 8000 instead of the world. This prevents Docker's firewall from bypassing UFW.\n\nNext, start the container in detached mode and verify it's healthy. Set up Nginx as the public entry point, binding it to localhost port 8000. Obtain an HTTPS certificate using Certbot. To roll back updates safely, build a new image with a new tag, start it on a different localhost port, wait for its health check to pass, then switch Nginx to the new port and reload. Keep the old image for easy rollback.\n\nShipOwn is a desktop app that automates this process. It works with any GitHub branch or local folder and builds Dockerfiles or Compose files on the server. Images are labeled with their commit source, and Nginx routes to localhost when configured. ShipOwn also handles HTTPS certificates and keeps the previous container running until the new one passes health checks. It's simple to use, requiring only SSH and shell commands.",
  "summary": "\"It works in Docker on my laptop\" is a great start. Getting that container onto a real server, behind a domain, with HTTPS and a way back when an update breaks, is where many small teams stall. Usually because nobody on the team is \"the DevOps person\". You don't need one for a single server. This guide takes a Dockerfile or Compose project from your repo to a live HTTPS URL in six steps, explains…",
  "key_points": [
    "Install Docker and Compose on Ubuntu using Docker's official repository.",
    "Use ShipOwn desktop app to automate deployment with HTTPS and rollback capabilities."
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}