You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -140,7 +140,7 @@ Be sure to view the following repositories to understand all the customizable op
140
140
|`MANUAL_RUN_FOREVER`|`TRUE` or `FALSE` if you wish to try to make the container exit after the backup |`TRUE`|
141
141
|`TEMP_LOCATION`| Perform Backups and Compression in this temporary directory |`/tmp/backups/`|
142
142
|`DEBUG_MODE`| If set to `true`, print copious shell script messages to the container log. Otherwise only basic messages are printed. |`FALSE`|
143
-
|`CREATE_LATEST_SYMLINK`| Create a symbolic link pointing to last backup in this format: `latest-(DB_TYPE)-(DB_NAME)-(DB_HOST) |`TRUE`|
143
+
|`CREATE_LATEST_SYMLINK`| Create a symbolic link pointing to last backup in this format: `latest-(DB_TYPE)-(DB_NAME)-(DB_HOST)`|`TRUE`|
144
144
|`PRE_SCRIPT`| Fill this variable in with a command to execute pre backing up ||
145
145
|`POST_SCRIPT`| Fill this variable in with a command to execute post backing up ||
146
146
|`SPLIT_DB`| For each backup, create a new archive. `TRUE` or `FALSE` (MySQL and Postgresql Only) |`TRUE`|
@@ -171,9 +171,9 @@ Your Organization will be mapped to `DB_USER` and your root token will need to b
171
171
|| Absolute HHMM, e.g. `2330` or `0415`||
172
172
|| Relative +MM, i.e. how many minutes after starting the container, e.g. `+0` (immediate), `+10` (in 10 minutes), or `+90` in an hour and a half ||
173
173
|`DB_DUMP_TARGET`| Directory where the database dumps are kept. |`${DB_DUMP_TARGET}/archive/`|
174
-
|`DB_DUMP_TARGET_ARCHIVE`| Optional Directory where the database dumps archivs are kept. |
174
+
|`DB_DUMP_TARGET_ARCHIVE`| Optional Directory where the database dumps archives are kept. |
175
175
|`DB_CLEANUP_TIME`| Value in minutes to delete old backups (only fired when dump freqency fires). 1440 would delete anything above 1 day old. You don't need to set this variable if you want to hold onto everything. |`FALSE`|
176
-
|`DB_ARCHIVE_TIME`| Value in minutes to move all files from `DB_DUMP_TARGET` to `DB_DUMP_TARGET_ARCHIVE` - which is useful when pairing against an external backup system. |
176
+
|`DB_ARCHIVE_TIME`| Value in minutes to move all files files older than (x) from `DB_DUMP_TARGET` to `DB_DUMP_TARGET_ARCHIVE` - which is useful when pairing against an external backup system. |
177
177
178
178
- You may need to wrap your `DB_DUMP_BEGIN` value in quotes for it to properly parse. There have been reports of backups that start with a `0` get converted into a different format which will not allow the timer to start at the correct time.
0 commit comments