-
Notifications
You must be signed in to change notification settings - Fork 2
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.
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
feat(deployment): basic http auth for website #2191
Conversation
I really like the idea of having this for the preview instances - how easy would it be to keep this for the preview instances when we go live and remove it for production? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Amazing - great and very fast work, Theo!
It could be possible, but it wouldn't really accord with an open source / open development model IMO. |
Adds configurable basic HTTP auth for the website only. If a
basicauth
secret is configured, which can be done as shown here (one could also use a sealed secret, one would have to generate its contents withhtpasswd
then seal it).N.B. This does not protect all data, which can still be accessed e.g. with LAPIS or potentially the backend.
This will apply to all preview instances but not to e.g. the pathoplexus demo until configured.
https://auth.loculus.org/
username: loculus
password: widetailpotato