Closed Bug 907940 Opened 11 years ago Closed 11 years ago

[prod] add WSGIPythonHome to mod_wsgi apache configs

Categories

(Infrastructure & Operations Graveyard :: WebOps: Socorro, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rhelmer, Assigned: bburton)

References

Details

Same as bug 907922 but for production:

We are switching to virtualenv (instead of our hacky vendor-dir-ish thing, known as "thirdparty").

For this to work we just need this directive in Apache on stage:

WSGIPythonHome /data/socorro/socorro-virtualenv

I've tested this on dev and it works ok - there's a socorro PR on our side that needs to land, no reason to wait on this though.
This should go out with Socorro 57
Assignee: server-ops-webops → bburton
Sorry :( to clarify, this is needed for:

crash-reports
socorro-mware

It's not needed for crash-stats
Specific files to Update:

crash-reports: modules/socorro/files/prod/etc-httpd-confd/crash-reports.mozilla.com.conf

mware: modules/socorro/files/prod/etc-httpd-confd/socorro-mware.mozilla.com.conf

Add 'WSGIPythonHome /data/socorro/socorro-virtualenv' to the top, outside the <VirtualHost> block
Blocks: 910483
This was deployed with today's release and is confirmed working.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.