Small updates to readme from starting up from scratch (#2086)

- Gitignore the directory where test files are uploaded
- Default superadmin password only used in dev / database auth environment

.gitignore

@@ -14,9 +14,11 @@
 # Ignore all logfiles and tempfiles.
 /log/*
 /tmp/*
+/public/tmp/*
 fits.log
 !/log/.keep
 !/tmp/.keep
+!/public/tmp/.keep
 spec/fixtures/proquest/output.xml
 
 # Ignore Byebug command history file.

README.md

@@ -57,8 +57,8 @@ person's uid to an environment variable called EMBARGO_NOTIFICATION_CC in the
     `git clone https://github.com/curationexperts/laevigata.git`
 1. Change to the application directory
     `cd laevigata`
-1. Use set your ruby version to **2.7.2** and the gemset of your choice
-    eg. `rvm use --create 2.4.2@laevigata`
+1. Set your ruby version to **2.7.2** and the gemset of your choice
+    eg. `rvm use --create 2.7.2@laevigata`
 1. Install gem dependencies
     `bundle install`
 1. Ensure you have `yarn` installed:
@@ -102,7 +102,7 @@ Each Emory school has its own AdminSet, which determines the approval process fo
 school, and who can approve deposited ETDs. Running `rake db:seed` will create an AdminSet for each school in the schools.yml file, load the appropriate workflow, and set permissions such that any registered user can deposit. `rake db:seed` should be idempotent -- you can run it over and over again safely.
 
 A "superuser" can manage all admin_sets, edit all ETDs, and approve submissions
-everywhere. To create a new superuser, add the user's email address to the `config/emory/superusers.yml` file. Then run `rake db:seed` to reload the config. Until we get real authentication running, the password for all superusers is `123456`
+everywhere. To create a new superuser, add the user's email address to the `config/emory/superusers.yml` file. Then run `rake db:seed` to reload the config. When using database authentication, the password for all superusers is `123456`.
 
 Note: Do *not* run `bin/setup` except the very first time you setup the application, or if you need to wipe out everything in your development instance. It will wipe your database but leave your AdminSets in place, making a huge mess that you can't easily recover from.