Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

switch once env var to fit with others #318

Merged
merged 1 commit into from
Jun 30, 2024
Merged

switch once env var to fit with others #318

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,7 +75,7 @@ The following are the environment variables, CLI flags and configuration file op
| how often to do a dump or prune, in minutes | BP | `dump --frequency` | `DB_DUMP_FREQ` | `dump.schedule.frequency` | `1440` (in minutes), i.e. once per day |
| what time to do the first dump or prune | BP | `dump --begin` | `DB_DUMP_BEGIN` | `dump.schedule.begin` | `0`, i.e. immediately |
| cron schedule for dumps or prunes | BP | `dump --cron` | `DB_DUMP_CRON` | `dump.schedule.cron` | |
| run the backup or prune a single time and exit | BP | `dump --once` | `RUN_ONCE` | `dump.schedule.once` | `false` |
| run the backup or prune a single time and exit | BP | `dump --once` | `DB_DUMP_ONCE` | `dump.schedule.once` | `false` |
| enable debug logging | BRP | `debug` | `DEBUG` | `logging` | `false` |
| where to put the dump file; see [backup](./backup.md) | BP | `dump --target` | `DB_DUMP_TARGET` | `dump.targets` | |
| where the restore file exists; see [restore](./restore.md) | R | `restore --target` | `DB_RESTORE_TARGET` | `restore.target` | |
Expand Down
4 changes: 2 additions & 2 deletions docs/scheduling.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,8 +24,8 @@ The scheduling options have an order of priority:

You can set it to run just once via:

* Environment variable: `RUN_ONCE=true`
* CLI flag: `dump --run-once`
* Environment variable: `DB_DUMP_ONCE=true`
* CLI flag: `dump --once`
* Config file:
```yaml
dump:
Expand Down
2 changes: 1 addition & 1 deletion test/test_restore.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@ docker container create \
-e DB_SERVER=mysql \
-e DB_USER=$MYSQLUSER \
-e DB_PASS=$MYSQLPW \
-e RUN_ONCE=1 \
-e DB_DUMP_ONCE=1 \
-e MYSQLDUMP_OPTS="${MYSQLDUMP_OPTS}" \
${BACKUP_IMAGE})
docker container start $cid_dump
Expand Down
Loading