On 2015-03-04 14:28, Rick Beemsterboer wrote:
> Hi hippo's,
>
> At my current project the customer would like to be able to do production
> deploys during the day. One of the main issues with this is there always needs
> to be a content freeze of some sort; a time period in which editors do not make
> any changes to the content, because changes made during the deployment will be
> lost.
> Currently the time it takes to backup the db, restore it on pre-prod, build
> indexes, etc takes a couple of hours. During this time editors cannot use the
> cms, which is unacceptable during office hours. We're looking at ways of
> minimizing this period, making daytime deploys possible.
There are several ways and strategies to shorten this period, but this typically
also requires special knowledge and handling depending on the project and
customer requirements.
If desired Hippo can provide consultancy and implementation support for this.
>
> I vaguely remember a talk from someone at Hippo (though I could be remembering
> this wrong ;-)), about tooling that makes it possible to (for instance) export
> all content created after a certain timestamp. Tooling like that could enable us
> to get an export of all changes made during a deployment, to import on our
> pre-prod environment. This could theoretically bring the content freeze window
> down to minutes instead of hours.
>
> So, does any tooling like this exist or is this something that's being worked
> on? How do others deal with content freezes and keeping them as short as possible?
This is an upcoming Enterprise feature indeed.
You can contact the designated account manager for your customer for more
information if you'd like.
Kind regards,
Ate Douma
Hippo Engineering Platform team
>
> Thanks,
> Rick
>
> --
> Rick Beemsterboer
> Sr. Java Developer
> HintTech Mastering the value of content <
http://www.hinttech.com/>
> Mastering the value of content
> creative | technology | content
> Delftechpark 37i
> 2628 XJ Delft
> The Netherlands
> T: +31 88 268 25 00
>
> M: +31 6 502 781 27
>
> Website <
http://www.hinttech.com/> Twitter <
https://twitter.com/HintTech>
> Facebook <
http://www.facebook.com/HintTech> LinkedIn
> <
http://www.linkedin.com/company/HintTech>
>
>
> --
> Hippo Community Group: The place for all discussions and announcements about
> Hippo CMS (and HST, repository etc. etc.)
>
> To post to this group, send email to
hippo-c...@googlegroups.com
> RSS:
https://groups.google.com/group/hippo-community/feed/rss_v2_0_msgs.xml?num=50
> ---
> You received this message because you are subscribed to the Google Groups "Hippo
> Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an email
> to
hippo-communi...@googlegroups.com
> <mailto:
hippo-communi...@googlegroups.com>.
> Visit this group at
http://groups.google.com/group/hippo-community.
> For more options, visit
https://groups.google.com/d/optout.
--
mailto:
in...@onehippo.com http://www.onehippo.com http://www.onehippo.org
Hippo B.V. The Netherlands Oosteinde 11, 1017 WT Amsterdam
+31 (0)20 522 4466
Hippo USA Inc. 745 Atlantic Ave, Third Floor, Boston MA 02111
+1 877 414 4776
_______________________________________________________________________________
This e-mail may be privileged and/or confidential, and the sender does not
waive any related rights and obligations. Any distribution, use or copying of
this e-mail or the information it contains by other than an intended recipient
is unauthorized. If you received this e-mail in error, please advise me (by
return e-mail or otherwise) immediately.