v1.0.1

What's Changed

• more rules to block bots from facets by @anarchivist in #70

Full Changelog: 1.0.0...v1.0.1

v1.0.0: Adds health checking to GeoData

• Add /health and /okcomputer endpoints for querying uptime and dependency statuses.

v0.0.8: Backend build updates

No functional changes, just a rebuild and update of the GitHub Actions workflows.

v0.0.7

Deploying tickets:
ADA-234: Ensure that the page, or at least one of its frames contains a level-one heading
ADA-231: Ensure that the page, or at least one of its frames contains a level-one heading
AP-388: Staging and production are't using app localized application name, they are using default values from Blacklight and GeoBlacklight

v0.0.6

Deploying accessible tickets:

1. ADA-233: Ensure landmarks are unique
2. ADA-235: The contrast ratio between a control's text and its background is not at least 4.5:1 on hover and/or on focus
3. ADA-239, 244: The TITLE element on this page does not identify the contents or purpose of the page
4. ADA-232: Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds

v0.0.5

Deploying tickets:

1. DEV-893: Add sitemap generator to geodata
2. DEV-912:Update GeoData's docker-compose.ci.yml to use !override
3. DEV-913: Resolve GitHub testing action issue

v0.0.4: Deploy AP-300: This includes multiple tasks, such as upgrading to GeoBlacklight v4.4.2

Deploy AP-300: This includes multiple tasks, such as upgrading to GeoBlacklight v4.4.2

Fixing: Calnet redirecting issue

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.