Application deployment you can verify, monitor and undo.

Deployableme covers the move from local to staging to production: CI/CD, Docker, containers, cloud hosting and the checks that tell you a release actually worked for users.

$ definition-of-done If you cannot deploy it safely, monitor it, and recover it, it is not really finished.

Stage 01/06

Application Deployment

Getting code onto a server is the easy part. The work is making it repeatable, so the fifth release goes as calmly as the first and a bad one can be pulled back in minutes.

Open the Application Deployment section →

From the DevOps.com wire

More from DevOps.com

Stage 02/06

DevOps

DevOps here means habits, not job titles: small changes, shared ownership of production, and fewer surprises at 2 a.m. We write for teams of two as much as teams of fifty.

Open the DevOps section →

Questions this section answers

  • [ ] Who gets paged when this breaks?
  • [ ] Is the runbook newer than the last incident?
  • [ ] Can one person ship without a meeting?

Stage 03/06

CI/CD

A pipeline is only as good as the checks inside it. We cover builds, tests and deploy steps in GitHub Actions and similar tools, and what each stage actually proves.

Open the CI/CD section →

Questions this section answers

  • [ ] Is the artifact built once and promoted?
  • [ ] Do tests cover the path users take?
  • [ ] Are secrets masked in the logs?

Stage 04/06

Production Readiness

The list between it runs and it's done: backups that restore, alerts that reach a person, certificates that won't lapse, and a rollback you've rehearsed. Our first article lives here.

Open the Production Readiness section →

InfoQ on DevOps practice

More from InfoQ - DevOps - Articles

Stage 05/06

Docker

Dockerfiles, images and compose files that build the same way on a laptop and a server. We focus on small images, pinned versions and keeping secrets out of image layers.

Open the Docker section →

Latest from Docker

More from Docker

Stage 06/06

Containers

Running containers once they leave your machine: health checks, restarts, resource limits, and the point where an orchestrator like Kubernetes starts to earn its complexity.

Open the Containers section →

Questions this section answers

  • [ ] Does the health check test the app, or just the port?
  • [ ] Are CPU and memory limits set?
  • [ ] Where do the logs go when a pod dies?

Before you start

Two questions we get first

What should I know before getting into application deployment?

Deployment is more than copying files to a server. You need a repeatable way to build the app, a place to test it, a safe way to handle secrets and configuration, and a plan for when a release goes wrong. Learn backups and rollbacks early, not after your first outage.

How much does application deployment cost in United States, Canada, United Kingdom, Australia, Europe, South Asia, Southeast Asia, Middle East, global English-speaking developer and technology markets?

The hosting bill is usually the small part. A static site can run on a free tier or a plan costing a few dollars a month, while a containerized app with a managed database and monitoring costs far more, and cloud providers price each region separately, so check the one you deploy to. The bigger cost in every market is engineering time: building pipelines, testing releases and handling incidents.

Follow on Google News