Changes

Nucleus is a Django (Playdoh) project intended to house numerous [[Websites/Mozilla.org/Publishing#SubProjects | subprojects]], each intended to publish a distinct type of templatized contentfor publication in Bedrock (www.mozilla.org). Nucleus resides on the stackato PaaS and exposes a public API (for reads) and an authenticated API (for writes), as well as a user interface in Django's standard /admin. All content entered into Bedrock will query the Nucleus API periodically, consume the JSON found there, save it in Bedrock's database, and then serve that data when users request those pages. Other applications may query the Nucleus API too for their own publishing needs; its data will be public. Why decouple nucleus from bedrock? * different access control; keeping bedrock very protected from multiple users, multiple environments* we're not ready to enable /admin or handle sessions in Bedrock* different SLAs; nucleus admin does not require the same uptime* separate content from publishing; nucleus serves data to multiple consumers* allow demo/dev/stage to pull in production-quality data Why use a local (in Bedrock) copy of nucleus data? * we don't want to rely on the nucleus system for realtime responses Why put the local copy in Bedrock's database? * the number of webheads means lots of copies of the same file if stored in filesystem; introducing potential for error