Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Small updates to readme from starting up from scratch #2086

Merged
merged 1 commit into from
Feb 24, 2021
Merged

Small updates to readme from starting up from scratch #2086

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down Expand Up @@ -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.

Expand Down
Empty file added public/tmp/.keep
View file
Open in desktop
Empty file.