Fixing: Calnet redirecting issue

downgrade omniauth to v1.0

Fixing: downgrade omniauth to v1.0

Downgrade omniauth to v1.0

v0.0.2: Production performance tuning

A few changes intended to improve performance / debug-ability in production:

1. Bumps Puma to v6. See their release notes for details, but in essence this was shown even in our own staging environment to significantly improve throughput.
2. Allows setting min/max Puma threads independently. We originally followed Heroku's guidance of setting these to the same value, but in our environment it makes sense to allow Puma to reap unused threads to free up resources.
3. Adds structured (JSON) logs via the Berkeley logging gem and disabled deprecation warnings (from Blacklight).

v0.0.1: Initial production release

This initial release includes changes to the Puma, Rack, and Logging configurations to better support concurrent usage in a production environment:

• Use ENV.LOG_LEVEL to set the logging level.
• Use PUMA_WORKERS and PUMA_THREADS to tune Puma's workers and threads, respectively.
• Adds the rack-timeout gem to ensure very long-running child processes are timed out.

Initial tests at UC Berkeley show this release significantly reduces CPU consumption and allows more concurrent users to be served per container than previous versions.