.gitignore

@@ -1 +0,0 @@
-*.sw*

README.md

@@ -9,8 +9,6 @@ The following are backed-up:
 * The MariaDB database (via a dump)
 * The `originals` directory (depending on where you mount the backup volume)
 
-Note: only backing-up the `originals` directory may not be sufficient. However, in my use-case, this backup system serves as a last resort, and I know I can re-generate other required files from the original data.
-
 ## Motiviation
 
 Whilst Photoprism provides [its own backup facility](https://docs.photoprism.app/getting-started/advanced/backups), I wanted something that I could easily run/manage using a separate container.
@@ -20,12 +18,14 @@ Whilst Photoprism provides [its own backup facility](https://docs.photoprism.app
 Simply write a `docker-compose.yml` along the following lines:
 
 ```
+version: '2'
+
 services:
   photosbackup:
     image: wilw/photoprism-backup
     restart: always
     volumes:
-      - /path/to/originals:/photoprism/originals # Mount a parent directory instead to backup more than just the originals
+      - /path/to/originals:/photoprism/originals
     environment:
       - PHOTOPRISM_DATABASE_SERVER=mariadbUri
       - PHOTOPRISM_DATABASE_NAME=photoprism
@@ -42,7 +42,7 @@ services:
 
 **Before bringing the container up, please read the following:**
 
-Please remember to change the variables in the `environment` block:
+Please remembeer to change the variables in the `environment` block:
 
 * `PHOTOPRISM_DATABASE_*`: Connection details to your Photoprism MariaDB server. This is easier if you include the `photosbackup` service in the same `docker-compose.yml` as your other Photoprism components.
 * `RESTIC_REPOSITORY`: The repository name. For a Linode Object Storage bucket you can use `s3:eu-central-1.linodeobjects.com/bucket-name`. See below for other examples.