|
Revision 43, 1.0 kB
(checked in by bradfitz, 4 years ago)
|
|
notes, docs
|
| Line | |
|---|
| 1 | -- you should be able to restore without setting up a config file. |
|---|
| 2 | if you lost data, that'd be annoying. restoring from a config |
|---|
| 3 | file will be supported in the future, but it's not yet. |
|---|
| 4 | |
|---|
| 5 | -- backups must be automatable, never requiring user input. hence public |
|---|
| 6 | key encryption. |
|---|
| 7 | |
|---|
| 8 | -- restores may prompt for user input ("What's your Amazon S3 |
|---|
| 9 | password?" and "Enter your GPG passphrase."), because they won't be |
|---|
| 10 | automated or common. and I don't want a restore to require a fully |
|---|
| 11 | setup ~/.brackup.conf. You probably lost it anyway. So a *.brackup |
|---|
| 12 | metafile (the one you get after a backup) should contain all the |
|---|
| 13 | metadata necessary to restore (say, Amazon S3 username), but not |
|---|
| 14 | secret stuff. |
|---|
| 15 | |
|---|
| 16 | -- targets shouldn't include passwords (say, Amazon S3 password) |
|---|
| 17 | in the *.brackup (backup "index"/"meta" file). let the user |
|---|
| 18 | enter that on restore. you should, however, put in metadata |
|---|
| 19 | that'll ease restoring.... like Amazon username, or path, etc. |
|---|
| 20 | |
|---|
