Back to Blog

v0.22.0: Docker Compose Backups, Schedule Tasks, Logs

Mauricio Siu

Mauricio Siu

May 5, 20253 min read

v0.22.0: Docker Compose Backups, Schedule Tasks, Logs

It's been over a month since our last major update. Sometimes, taking a small break to recharge and develop features with renewed energy is exactly what's needed.

This update brings functionality that unlocks many previously missing use cases, and we can now confidently say that we cover almost any scenario. Let's dive into what's new!

Docker Compose Backups

Previously, we only had dedicated backups for Docker Swarm services. While this approach had its advantages (like maintaining unique entities and easier manipulation), it also had limitations. For complex templates like Umami, Plausible, and many others, it was cumbersome to separate containers into individual services.

Now, you can backup containers within a Docker Compose or Docker Stack file! We've added support for:

  • PostgreSQL
  • MariaDB
  • MySQL
  • MongoDB

And yes, this includes restore functionality too!
We've also integrated logging for each backup operation. Before, we couldn't track if executions were running correctly or not. Now, you'll have detailed logs for every backup performed.
No more excuses for not using Docker Compose because of missing backup capabilities!

Schedule Tasks

We consider this one of our most important features as it unlocks almost any use case that wasn't possible before. Schedule Tasks are essentially cron jobs with custom code that run on specific containers or servers.

We offer three ways to declare cron jobs:

  1. Applications: Generate schedules for application-based services
  2. Docker Compose Services: Create schedules for specific services defined in your Docker Compose file
  3. Server Tasks: Create schedule jobs for your Dokploy server or remote server

Real-World Example

Let's say you have a Next.js application and want to run cron jobs. Currently, this is possible in Vercel, but it requires creating a custom server and unnecessary complexity. With Schedule Tasks, you can trigger any command in your containerized project.

For instance, if you have an API endpoint /send-notifications-every-12-hours that sends external notifications, you could create a schedule task with:

This will trigger the endpoint without hosting the service on Vercel or creating more complex solutions.

Server Schedule Use Cases

Some practical examples include:

  • Automated Docker storage cleanup
  • Custom backups for unsupported databases (like Plausible)
  • Triggering endpoints using curl commands

Domain Management Improvements

We've redesigned the domains section to include DNS validation. Often, when something doesn't work, it's because DNS isn't properly propagated or is pointing to the wrong server. Now you can:

  • Validate if DNS is correctly pointing to your Dokploy or remote server
  • Access step-by-step instructions for adding A records in DNS providers

Bug Fixes:

  1. Fixed Gitea provider repository and branch fetching
  2. Eliminated race conditions during Dokploy instance backups
  3. Support for two deployment trigger methods on applications: on push and on tag

Thank You for 20K Stars! 🎉

Today marks an incredible milestone for Dokploy - we're approaching 20,000 GitHub stars! It's hard to believe that exactly one year ago, on May 1st, 2024, I made the first commit to this project. The journey since then has been nothing short of amazing.

This achievement wouldn't have been possible without our incredible community. Your continuous support, recommendations, and contributions have helped shape Dokploy into what it is today. Every star, every piece of feedback, and every contribution has played a crucial role in making Dokploy better.

We have a big announcement coming in a couple of weeks, stay tuned!

Thank you all! ❤️

Support Dokploy

If Dokploy has helped you, consider sponsoring us to maintain this incredible project! And if you'd rather not deal with server administration or errors, try our cloud version - perfect for those who don't have time to manage containers and related issues ❤️

https://opencollective.com/dokploy
https://github.com/sponsors/Dokploy

Release notes: https://github.com/Dokploy/dokploy/releases/tag/v0.22.0

Related Posts

v0.21.0: Gitea Provider, Backups and Restore for Dokploy, Duplicate services

v0.21.0: Gitea Provider, Backups and Restore for Dokploy, Duplicate services

March 30, 20252 min read

We're thrilled to announce Dokploy v0.21.0, bringing exciting new features to enhance your deployment workflow! This release introduces a Gitea provider, backup and restore capabilities for Dokploy itself, and the ability to duplicate services. Gitea Provider You can now use Gitea as a provider for your Dokploy deployments! This allows you to seamlessly integrate your Gitea repositories with Dokploy, streamlining your deployment process. Backups and Restore for Dokploy We've added the ab

v0.20.0: Watch Paths, Remote Templates, Auto Backups Cleanup

March 11, 20252 min read

We are excited to announce Dokploy v0.20.0, packed with major improvements, new features, and a revamped template system! This release brings better automation, flexibility, and usability enhancements to streamline your deployments. HTTP3 Support for Traefik have migrated from Docker Swarm service to a standalone container for Traefik, which now supports HTTP3 by default for new installations. Existing installations will need to update their traefik.yml configuration: entryPoints: web:

v0.19.0: Organizations, AI-Powered Deployments & More!

v0.19.0: Organizations, AI-Powered Deployments & More!

March 3, 20252 min read

The latest Dokploy release, v0.19.0, introduces significant updates, including organizations, an AI-powered Docker Compose generator, improved authentication, and a redesigned API keys system. Additionally, Dokploy Cloud now supports GitHub and Google authentication for a smoother login experience. New Features: Organizations Dokploy now supports multiple organizations, allowing users to better isolate and manage their resources. This is useful for teams working on multiple projects or mana