various updates

Author: dunkOnIT

contributing/quickstart.md

@@ -19,7 +19,7 @@ Now the website will run locally. You have some options on how to set up the dat
 ## (2) DATABASE SETUP
 There are two options here - a "test" database with generated data, or the production database (with sensitive information removed).
 1. **Test database**: Quick to set up, but may not mirror real-world data well. `docker exec -it rails bash -c "bin/rake db:reset"`
-2. **Exported database**: Takes 60-90 minutes to set up, but uses actual data from the live website. `docker exec -it rails bash -c "bin/rake db:load:development"`
+2. **Exported database**: Takes 60-90 minutes to set up, but uses actual data from the live website. `docker exec -it rails bash -c "bin/rake db:load:development[reload]"`
 
 ## (3) RUNNING TESTS
 Two options - running while your docker server is running, or running tests independently. 

wst-processes/common_requests.md

@@ -34,3 +34,9 @@ AWS will send an email with the title "Action Required - Your certificate renewa
 3. Click on the certificate with the relevant name in the "Domain name" column
 4. Click "Create records in Route 53"
 5. Confirm with "Create records"
+
+# Resetting a Password
+
+We never reset a password on someone's behalf - they should use the built-in password change feature.
+
+# Transferring an Account

wst-processes/internal_processes.md

@@ -120,3 +120,34 @@ For example, `3.2.1` --> `4.0.0` (first digit)
 You should skim the changelog for any breaking changes that could be relevant.
 If it's a crucial part of our infrastructure (see above), get a second pair of eyes to review.
 
+# Removing Duplicate Motions
+
+Motions are stored in an S3 bucket: 
+
+Currently, motions are not deleted when a new set is deployed. We have to delete them manually, and clear the cache key.
+1. Delete the old file 
+    1. Navigate to: https://us-west-2.console.aws.amazon.com/s3/buckets/wca-documents?region=us-west-2&bucketType=general&prefix=documents%2Fmotions%2F&showversions=false&tab=objects
+    1. Select the file and select delete
+    1. Confirm that you are targeting the correct file, and enter "permanently delete"
+1. Clear the cache
+    1. Connect to the production instance
+    1. Enter the rails console with `bin/rails console`
+    1. Find the cache key for the documents list with the following code:
+    ```ruby
+    Rails.cache.redis.with do |redis|
+      cursor = "0"
+      keys = []
+      loop do
+        cursor, batch = redis.scan(cursor)
+        keys.concat(batch.select { |key| key.include?("documents") })
+        break if cursor == "0"
+      end
+      keys
+    end
+    ```
+    1. Optionally, run `rails.cache.read(cache_key_from_previous_command)` to confirm you are targeting the correct key
+    1. Run `rails.cache.delete(cache_key_from_previous_command)`
+
+## How are motions deployed? 
+
+