Does that affect the warranty? Do you touch the database directly? Sounds like a nice solutions customized for a single client, I doubt that this can be used as a general solution without a lot customizing. But still. Might be worth a look at.
On 19 Aug., 09:24, "Christian Burne" <[email protected]> wrote: > We've developed our own proprietary tool for release management between serer > environments. It allows us to release Content Classes, Workflows, > Authorization pkgs and Cats & Keywords. > > It's super useful/required in an enterprise environment where you have 4 plus > distinct environments to manage and keep synchronized. > > > Christian Burne - Oshyn, Inc. - Powering Innovation ™ > > Direct 213.784.5322 | Cell 714.865.8926 | Fax 213.612.0291 | > Web www.oshyn.com > > > > Follow Oshyn on... Twitter & LinkedIn > > Check out our latest client success -www.lstudio.com > > Nick Galotti wrote: > > Over the years we have learned the hard way that developing RQL on the > > production RedDot server isn't a good idea because it could > > potentially require a reboot. We are thinking of developing templates > > in a development RedDot server but we don't know the best way to bring > > the developed code/content classes over to production, especially for > > upgrading existing content classes. > > We are aware of exporting/importing content classes, but is this the > > best way? What about when developing large amounts of code? > > Does anyone have experience in this? > > -Nick --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en -~----------~----~----~----~------~----~------~--~---
