docs: add details about uploads import/export/backup scripts

README.md

@@ -165,6 +165,18 @@ You can export your database for another developer to import or to import to a s
 
 This will happen automatically when you import a database, but if you want to manually backup your database, you can run `npm run backup:db`. This functions nearly identically to the `export:db` script, except for using a different prefix and putting the file in `sync/sql/backups`. As with `export:db`, you can specify a name for your DB backup if you want.
 
+#### Importing Uploads
+
+You can import a zipped copy of the `uploads` folder from another environment, saved backup, or another developer's export with the `import:uploads` script. To use it, put a `*.tar.gz` file in a top-level `sync/uploads` folder in the repo and run `npm run import:uploads`. This will first back up your current `uploads` folder in case you need those files back, and then it will replace your `uploads` folder with the contents of the zip file.
+
+#### Exporting Uploads
+
+You can export your `uploads` folder for another developer to import or to import to another environment by running `npm run export:uploads`. By default, this will create a timestamped zip file in `sync/uploads/exports`, but you can specify a name by running `npm run export:uploads <your-descriptive-name-here>`. The exported file will still be timestamped, but it will use the name you give it instead of the default prefix.
+
+#### Backing Up Uploads
+
+This will happen automatically on import, but if you want to manually backup your `uploads` folder, you can run `npm run backup:uploads`. This functions nearly identically to the `export:uploads` script, except for using a different prefix and putting the zip file in `sync/uploads/backups`. As with `export:uploads`, you can specify a name for your backup if you want.
+
 ### Atom
 
 If you use Atom, go to Preferences > Packages. Open the `language-php` Core Package settings. Go to the Tab Type setting and set the drop down option to `hard`.