Releases, Containers and Backups

This service is for a project that is deployed by hand, runs without containers, or has no backups. I set up automated releases, package the application in Docker, deploy the services you need on your server and build backups you can actually restore from.

Once it is set up, ssh + git pull + docker restart is no longer needed: code passes the tests, is built into an image and deployed to the server on every push to the repository.

What you can order

Prices are per project. If you need several rows at once, for example containers, CI/CD and backups for one application, we agree on a single price before work starts.

How the work goes

1. You describe the stack, how you deploy now and what you want to get, and give access to the repository and the server.
2. I propose a scheme: CI/CD platform, deployment method (Kamal, Docker Compose or SSH), backup destination and schedule.
3. I set it up, run it on real data and check it: the pipeline passes, containers come back after a restart, a backup restores.
4. I hand over a description of what is configured and how to use it.

If you are not sure which self-hosted service fits your task, I will recommend one before we start.

Related articles

These materials show how I approach the setup. You can read them before ordering.

CI/CD and deployment

• Secure Development: Part 1 — CI/CD: From Manual Deployments to Automated Deployment
• Configuration and Secrets Management in GitHub Actions: A Systematic Approach
• Modern Next.js deployment: GitHub Actions, Docker, and Zero-Downtime
• Deployment Platforms: Part 5 — Kamal: deploying Docker applications to your own server

Docker and Docker Compose

• Secure Development: Part 5 — The Proper Dockerfile
• Secure Development: Part 6 — Container Security
• Logrotate and Docker: Why and How?
• Dockge vs Portainer: what Dockge is and why I switched

Self-hosted services

• Vaultwarden: self-hosting a password manager in 30 minutes
• Self-Hosted Cloud: Part 1 — File Storage on Nextcloud
• Self-hosted cloud: Part 5 — Immich instead of Google Photos
• TrueNAS in 2026: Is It Worth It? Community Edition vs CORE, Hardware, ZFS

Backups

• Backup: Part 2 — The 3-2-1 Rule and Its Modern Variant
• WordPress backup to Yandex Cloud: mysqldump, rclone, and Telegram notifications

FAQ

What access do you need?

For CI/CD, a repository on GitHub or GitLab and SSH to the server. For Docker and self-hosted services, SSH to the server. For backups, SSH and the details of the storage where copies will go.

What if I have no server?

You can get one at BigMike Cloud, VPS from $15 per month. A home server or a NAS running Linux also works.

Do I have to choose the CI/CD platform in advance?

No. I work with GitHub Actions, GitLab CI and Gitea Actions, and deploy with Kamal, Docker Compose or SSH depending on the stack. We agree on the choice after you describe the project.

Where are backups stored?

In S3-compatible storage or on a remote server: Yandex Object Storage, Backblaze B2, Hetzner Storage Box. Copies are encrypted and rotated automatically, and the result arrives as a Telegram notification.

Is this a one-time job?

Yes. More about the tasks: CI/CD setup and backup for business.

How to order

Write on Telegram @BigMike_help: briefly describe the project and what needs to be set up. I reply on the next business day. Other ways to get in touch are on the contacts page.