Gate the site behind HTTP Basic Auth for pre-release#33
Merged
Conversation
The app is deployed but not ready for public release, so add a coarse shared-password lock in front of the whole site, on top of the existing session auth. - ApplicationController runs http_basic_authenticate_with in production only, reading credentials from Rails encrypted credentials. The /up health check is unaffected (Rails::HealthController doesn't inherit it), so Kamal proxy health checks keep working. - Store the basic_auth username/password in environment-specific production credentials (config/credentials/production.yml.enc). - .kamal/secrets pulls RAILS_MASTER_KEY (the production key) from 1Password with an env-var fallback. - Ignore config/credentials/*.key so the production key is never committed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The app is deployed but not ready for public release, so this adds a coarse shared-password HTTP Basic Auth lock in front of the entire site, layered on top of the existing session auth.
ApplicationControllerrunshttp_basic_authenticate_within production only, reading the username/password from environment-specific Rails credentials (config/credentials/production.yml.enc); the/uphealth check is unaffected sinceRails::HealthControllerdoesn't inherit from it, so Kamal proxy health checks keep working..kamal/secretsnow pullsRAILS_MASTER_KEY(the production key) from 1Password with an env-var fallback, and.gitignoreexcludesconfig/credentials/*.keyso the production key is never committed. Dev and test environments stay open, so the existing Minitest suite is unaffected.🤖 Generated with Claude Code