Closed Bug 983741 Opened 11 years ago Closed 11 years ago

[bedrock] Remove basic auth from demo2

Categories

(Infrastructure & Operations Graveyard :: WebOps: Product Delivery, task)

Product:
Infrastructure & Operations Graveyard
Component:
WebOps: Product Delivery
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: pmac, Assigned: cturra)

Details

Please remove the basic auth config stanza from the www-demo2.allizom.org config. Do NOT delete the password file at /etc/httpd/mozilla/domains/www-demo2_password. We've added the config to the demo.conf apache config file in the bedrock repo so that we can turn it on and off per demo branch. https://github.com/mozilla/bedrock/blob/master/etc/httpd/demo.conf
as requested, i have removed just the apache basic auth configurations on demo2 so you can manage password protection through the demo.conf in github. let me know if you'd like this same setup applied to the other demo instances?
Assignee: server-ops-webops → cturra
Flags: needinfo?(pmac)
To my knowledge the other demos do not have a password config, but should one be pushed to any of them via demo.conf in a branch it should work. Are there other config changes necessary on the other demos to make it work?
Flags: needinfo?(pmac) → needinfo?(cturra)
you're right, i was under the impression that they all had a basic auth prompt applied to their /. i should have looked. they all include the demo.conf, so keep in mind, if you turn on basic auth for one, it will apply to them all.
Flags: needinfo?(cturra)
I think it shouldn't. Since that demo.conf file is in git, it can (and will) be different per branch. When we push a branch to a demo via chief it will include whatever is in that branch's demo.conf. I believe that each demo apache config loads in the demo.conf from the specific directory for the code deployed for that demo. So each should be able to have their own config at a given time, much like they do for testing changes to global.conf. Please correct me if I'm wrong though. I've only really thought all of this through this afternoon :)
good call, i never considered you have different git branches for different demo environments. in that case, i don't see any issues (or outstanding action items) here.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Great! Thanks again :cturra!
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.