Closed Bug 959087 Opened 10 years ago Closed 10 years ago

Deploy ReMo instance in stackato

Categories

(Mozilla Reps Graveyard :: reps.mozilla.org, task)

Product:
Mozilla Reps Graveyard
Component:
reps.mozilla.org
Platform:
x86_64
Linux
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: nemo-yiannis, Assigned: nemo-yiannis)

Details

(Whiteboard: [kb=1237726] [qa-]) 

Since we will be focusing more on our workflow towards continuous deployment, let's deploy reps to stackato to make the launch of new development environments easier.
Whiteboard: [kb=1237726]
Group: mozilla-reps-admins
Assignee: nobody → jgiannelos
Status: NEW → ASSIGNED
Commits pushed to master at https://github.com/mozilla/remo

https://github.com/mozilla/remo/commit/b4ce89c614336adb929ad7b2d5196fd3a9483f9a
[Fix bug 959087] Add configuration to enable stackato deployment.

* Add stackato.yml
* Add example local.py settings for stackato
* Enable rabbitmq/memcached services
* Add stackato requirements file
* Setup uwsgi process to serve static files
* Setup HTTPS proxy

https://github.com/mozilla/remo/commit/07cc3de3d55660bf986bc05a252755096e054f4c
[bug 959087] Update stackato conf.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Version: unspecified → next
Whiteboard: [kb=1237726] → [kb=1237726] [qa-]
Version: next → 427
Product: Mozilla Reps → Mozilla Reps Graveyard
You need to log in before you can comment on or make changes to this bug.