Closed Bug 720473 Opened 12 years ago Closed 12 years ago

Setup production server for ReMo

Categories

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

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: pierros, Assigned: jd)

References

Details

Hello IT!

We would like to have our production environment setup under reps.mozilla.org

More info in Mana here: https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=1082416 and here: https://wiki.mozilla.org/ReMo/Website

Thanks!
Blocks: 718489
Assignee: server-ops → jcrowe
Depends on: 721552
Pierros,

This is done except https:// does not work yet.  I filed bug 721552 for the cert.

FYI celery has been tested here and is working.

Regards
Status: NEW → ASSIGNED
The SSL cert has been installed and tested.  This should be finished now.  Please let me know if you see anything amiss.

Regards
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Please also add memcached.

Thanks!
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Giorgos,

Memcache has been configured for prod.  I did not push this out but it will go to the web nodes on the next prod push.

Regards
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
Please add a cronjob to update product details once per week.

./manage.py update_product_details

I changed our mana page to reflect that.

Thanks!
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Added cron job to run once per week.

Note that the following error still occurs:

[root@engagementadm.private.phx1 remo]# ./manage.py update_product_details
Error: No module named memcache

So this cron job will not do anything until the site is updated.

Regards
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.