Typical dotCMS deployment architectures in the absence of syndication?

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Typical dotCMS deployment architectures in the absence of syndication?

Paul Fitchett
Hi,
Our current CMS has the concept of syndication - that is, being able to move content from server to server in a controlled fashion - in order to support preview, staging and production environments more easily.

I understand this was planned for the 1.9 release but didn't make the cut and is likely later in the year.

In the absence of a syndication capability, how do people handle preview and staging at the moment? Do they author directly into the production environment, or do they author into a staging environment and then backup and restore into production or do they do something else?

Cheers,
Paul Fitchett

P.S. thanks to everyone for the prompt helpful replies to my many questions - it is most appreciated!




------------------------------------

Need Help?  See:

http://www.dotcms.org/support 

for open source support options.Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/dotcms/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/dotcms/join
    (Yahoo! ID required)

<*> To change settings via email:
    [hidden email]
    [hidden email]

<*> To unsubscribe from this group, send an email to:
    [hidden email]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Reply | Threaded
Open this post in threaded view
|

Re: Typical dotCMS deployment architectures in the absence of syndication?

wezell-2
Administrator
Paul:

With the 1.9 move to UUIDs, it would not be hard to write a .sh script that
1) rsynced your ./asset directory from staging --> live and 2) sql copied
changes from staging ---> live.  You would have to go into the prod server
and flush cache and reindex, but it should work.  It would be a poor mans
solution to the push publishing, but it would make moving from staging to
prod much easier.




Will

----
Will Ezell
www.dotcms.org
phone: 305.858.1422 ext. 286
direct: 978.296.4239
skype: wezell1




On Tue, Feb 9, 2010 at 5:27 PM, [hidden email] <
[hidden email]> wrote:

> Hi,
> Our current CMS has the concept of syndication - that is, being able to
> move content from server to server in a controlled fashion - in order to
> support preview, staging and production environments more easily.
>
> I understand this was planned for the 1.9 release but didn't make the cut
> and is likely later in the year.
>
> In the absence of a syndication capability, how do people handle preview
> and staging at the moment? Do they author directly into the production
> environment, or do they author into a staging environment and then backup
> and restore into production or do they do something else?
>
> Cheers,
> Paul Fitchett
>
> P.S. thanks to everyone for the prompt helpful replies to my many questions
> - it is most appreciated!
>
>
>
>
> ------------------------------------
>
> Need Help?  See:
>
> http://www.dotcms.org/support
>
> for open source support options.Yahoo! Groups Links
>
>
>
>