Skip to content

docs(databases): document enabling Redis AOF persistence - #200

Open
anilonayy wants to merge 1 commit into
Dokploy:mainfrom
anilonayy:docs/redis-aof-persistence
Open

anilonayy wants to merge 1 commit into
Dokploy:mainfrom
anilonayy:docs/redis-aof-persistence

Conversation

@anilonayy

Copy link
Copy Markdown

Summary

Adds a short recipe to the Databases → Overview page showing how to enable Redis AOF persistence through Advanced → Run Command.

Why

A Dokploy Redis service starts with redis-server --requirepass <password> and no persistence flags, so it runs with Redis' built-in RDB defaults and the append-only file (AOF) is off. There is no dedicated persistence setting in the UI, and the way to turn AOF on (overriding Command/Args) is not documented. On a write-heavy instance this matters: the default RDB snapshotting can rewrite the dump far more often than expected.

What the recipe says

Set, under Advanced → Run Command:

  • Command: /bin/sh
  • Arguments: -c, then redis-server --requirepass "$REDIS_PASSWORD" --appendonly yes --save 3600 1

then Deploy. It references "$REDIS_PASSWORD" (which Dokploy already injects) instead of hardcoding the password, which also avoids quoting issues with special characters.

Verification

  • The default command and the injected REDIS_PASSWORD variable are taken from packages/server/src/utils/databases/redis.ts in the main repo.
  • I ran the exact Command/Args this page recommends against the default redis:8 image. CONFIG GET appendonly returns yes, CONFIG GET save returns the configured rule, and auth with the password works.
  • Docs-only change (one page, English). I did not run the full docs site build locally. A matching overview.cn.mdx update can follow if wanted.

@anilonayy
anilonayy force-pushed the docs/redis-aof-persistence branch from bb72c5f to d828b29 Compare October 12, 2026 07:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant