Foundation.mozilla.org: Improve deployment process

Created on 12 Sep 2017  路  6Comments  路  Source: mozilla/foundation.mozilla.org

What problem(s) are we trying to solve?

  • Making changes to the network site is error-prone.

    • There's a circular dependency in which the front end being built is dependent on the API being spun up, but that doesn't happen till the front end gets built.

    • Deploying changes is error prone- sometimes rebuilds fail silently on content updates

    • Production/Master branch setup is unlike our other projects, and it's helpful to have the same dev/deploy process as much as possible.

We need to solve these, keeping in mind that Mezzanine templating...isn't great or easy

(original etherpad)

Most helpful comment

Before closing this we're going to need to turn off the "rebuild on model change" script @cadecairos

All 6 comments

Before closing this we're going to need to turn off the "rebuild on model change" script @cadecairos

@alanmoo is this something we want now? I can disable it via config, and I can rip out the signals altogether.

Should be safe to turn off now that all the CMS driven components are pulling via XHR on prod.

filed #798 - I think I might leave that for next week, and just disable the build via config for now

The model signals will now bail early, as I've unset the config vars they rely on.

Closing epic, final issue has a PR open.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

sabrinang picture sabrinang  路  5Comments

kristinashu picture kristinashu  路  5Comments

kristinashu picture kristinashu  路  5Comments

kristinashu picture kristinashu  路  3Comments

kristinashu picture kristinashu  路  4Comments