Deprecate figs II

[the-codetrane]

Problem

figs is a proprietary config gem that has been abandoned and is blocking the Ruby/Rails upgrade

Solution

• use config gem instead
• use dot-env gem to manage ENV variables outside of Settings class

PR Type

• Feature
• Tests
• Janitorial (refactoring, dependency updates, etc.)

[mnyrop]

@the-codetrane some follow ups:

• How are these lines using ENV working? https://github.com/NYULibraries/spatial_data_repository/blob/6ac07672f22f4da77e00da1356ea9e5dca1e7fe4/config/database.yml#L5C3-L5C3 Presumably these should be changed to Settings as well, unless ENV is somehow mirroring Settings?
• What's the new workflow? Do config/vars.yml and config/vars.yml.example get deleted and we copy the secret vars file (from box) to /config/settings/production.yml on prod instead?

It would be great if you could write some notes on how you got this working on staging and where/what you changed in terms of vars/files within the EC2 so we can make sure its reproducible later.

[the-codetrane]

• How are these lines using ENV working? https://github.com/NYULibraries/spatial_data_repository/blob/6ac07672f22f4da77e00da1356ea9e5dca1e7fe4/config/database.yml#L5C3-L5C3 Presumably these should be changed to Settings as well, unless ENV is somehow mirroring Settings?

Yeah, these should be read in from Settings like all the other var's; updated.

• What's the new workflow? Do config/vars.yml and config/vars.yml.example get deleted and we copy the secret vars file (from box) to /config/settings/production.yml on prod instead?

Yes, we'll need to flatten vars.yml for production into a production.yml file that gets put into configs/settings. It'll also provide a nice separation of concerns to make sure only env-specific configs end up in prod.

So the main changes will be:

• in Box, remove vars.yml and replace it with production.yml with the production-specific key/value pairs
• cp production.yml config/settings

This should get the correctly-formatted file into the place where config will pick it up

[mnyrop]

@the-codetrane sounds good! Thanks for the write up. Just send me that production.yml file over Slack when you get the chance and I'll add it to Box.