Update TODO list and tidy up README

README.md

@@ -9,17 +9,25 @@ these problems:
  - You need to define all the volumes to back up in the configuration system
  - Backups require services to be stopped to take consistent copies
 
+Backupbot II tries to solve these problems by **letting you define how to back up your services using Docker labels**, so you can **easily collect your backups for use with another system** like docker-volume-backup.
+
 ## TODO
 
-- [ ] Make a Docker image of this
-- [ ] Rip out or improve Restic stuff
-- [ ] Add secret handling for database backups
+A first stab:
+- [x] Make a Docker image of this
+- [x] Add secret handling for database backups
+- [ ] SSH remote storage
+  - [ ] Add SSH key handling
+  - [ ] SSH host key checking
+- [ ] S3 remote storage
+- [ ] Re-add `crond` support
+
+Future:
 - [ ] Continuous linting with shellcheck
+- [ ] Rip out or improve Restic stuff
 
 ## Label format
 
-(Haven't done secrets yet, here are two options)
-
 ```
 services:
   db:
@@ -32,11 +40,3 @@ services:
         backupbot.backup.post-hook: "rm -rf /tmp/dump/dump.db"
         backupbot.backup.path: "/tmp/dump/"
 ```
-
-## Questions:
-
-- Should frequency be configurable per service, centrally, or both?
-
-```
-- "backupbot.backup.at: "* * * * *"
-```