recommendations on managing deployments

[craayzie]

How does everyone manage deployments of new pages/page_parts/layouts
(all of the presentation and application layer logic that sits in the
DB)? I don't see a simple way to separate out "real content" that say,
for example, authors would generate on the live site from this other
"application layer" content that a developer/designer would be working
with.

I'm hoping the answer is not:

1. taking down production
2. download production DB to dev/staging
3. add dev/staging tracked changes to the production DB download
4. deploy the merged DB above to production
5. bring production back up

Thanks as always :)

[Jonathan Camenisch]

I can definitely see why Nathaniel created the file_system_resources extension ( http://ext.radiantcms.org/extensions/148-file-system-resources ). Often template changes correspond with css changes, and the two should committed to your source code management repository as one snapshot.

I need to integrate that into my workflow soon. So far I've just been using heroku db:pull/push, or sometimes pasting straight into the live ui from the layout that's working on dev. It's less critical when you're working on a fresh brochure site that's not yet published.

--
Radiant CMS Dev Mailing List
Post:        radiant...@googlegroups.com
Unsubscribe: radiantcms-de...@googlegroups.com
Group Site:  http://groups.google.com/group/radiantcms-dev/