737925 - make chief easily portable to other sites

Status: RESOLVED FIXED

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

Description

[Jake Maul [:jakem]]

We have a growing number of requests to make sites self-pushed by webdev. The chosen way to do this so far (AMO, SUMO) is with chief. However, my understanding is that it is very difficult to set up, as it was written primarily with AMO in mind.

We need to make this easily configurable for any standard django site. At the very least, some good installation/setup documentation would be a good start.

Bedrock webdevs already have a request in for this... making it as dependent on this bug. We've had similar requests from other webdevs for their own smaller sites from time to time. It would be nice to be able to just fulfill these quickly and easily... even perhaps making it part of a standard site or admin node setup.

Comment 1

[Corey Shields [:cshields]]

Alternative to this would be good documentation on deploying chief..  we have quite a few devs begging for this.

Comment 2

[Jeremy Orem [:oremj]]

It's pretty generic right now. The project that will be deployed via chief just needs a commander script that has "pre_update", "update", and "deploy" tasks. Once those are ready you just have to add the app to "settings.py".

Comment 3

[Jeremy Orem [:oremj]]

Some docs are up at https://github.com/jbalogh/chief/ and internal docs at https://mana.mozilla.org/wiki/display/websites/Chief.

Let me know if you get stuck.