Supporting multiple envionments

[jjU]

Hello.

I am wondering if there is a way to support a workflow where the content is entered/stored in a development/test environment and exported-imported into a production environment. I want to provide a safe environment to create/edit content and then simply it push it out to production.

Any ideas?

Thanks.

[Ian Ward]

I second this idea,

Having a way to export a page or sub-tree of pages would be really
handy. I had to recreate a number of pages manually some time ago and
it was no fun. I'm not sure what should happen if the author of a
page doesn't exist on the target environment, default to the current
user, I suppose?

I'd suggest a tidy little JSON format that includes page details and
the latest Content body for each language and type and then a list of
all the child pages with the same. The UI could be Import+file
upload/Export buttons in the Page edit admin view.

I don't know when I'd be able to work on it, but is this the sort of
thing you're looking for?

Ian

> --
> You received this message because you are subscribed to the Google Groups
> "django-page-cms" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/django-page-cms/-/xyWqsWoTOjAJ.
> To post to this group, send email to django-...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-page-c...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-page-cms?hl=en.

[jjU]

Yeah totally, I could do it via a South data migration but that gets into the developer workflow. I would like it to be driven from the admin console, yeah JSON export and import would be ideal.

> To post to this group, send email to django-page-cms@googlegroups.com.

> To unsubscribe from this group, send email to

> django-page-cms+unsubscribe@googlegroups.com.