To this Mac
Taken every night at the time you choose, and the newest 14 backups are kept. The Mac has to be on at that time; Kule tells you this up front.
every nightlast 14 backupsLaunchAgent
Feature · Databases and backups
It takes the backup, then tries a restore.
It backs up your databases every night to this Mac or to an S3-compatible bucket. A backup coming to this Mac is first restored once on the server and tested before it arrives.
Two ways
To this Mac, or to a bucket.
You set up the schedule once. You see where it goes and when the last one was taken right on the card.
S3, R2, B2
Dokploy takes the backup and sends it to the bucket, so it works even when the Mac is off. Dokploy keeps the bucket keys, not Kule.
S3R2B2S3-compatible
Restore test
A PostgreSQL backup is restored into a temporary copy on the server and tested; the others get an integrity check. A broken backup is not brought to the Mac.
temporary containerintegrity
On every card
Everything about the database.
Size and connection count are read from the database's own container. Passwords never reach the interface.
Sizeread from inside the container
Connectionsopen connections and the limitclients, for Redis
Addresspostgresql://aktar:••••@aktar-db:5432/aktarshown without the passwordinternal network
Consolein the database's own containerread-only
Before deletingone last backup is taken to this Macif backups are on
Restorethe backup folder opensdone by hand for nowby hand
What it knows
The databases Dokploy runs.
Each one has its own card. A cache doesn't need a backup, and its card says so.
Backed up
Cache
Buckets
We'll let you know when Kule is out.
People on the list get the first version before anyone else.
You're on the list. You'll be the first to hear when Kule is out.