Yes we have done exactly this when we had problems getting content into a site whilst still developing it (we were on a very tight timescale and we had 15 content inputters with 2 developers trying to publish and work on the system).
Reddot is capable of running clustered and you just tell it which is the default publication server, it will help performance a great deal. Ours was getting unusable and once we did this it sorted it all out. It is also suprisingly easy to setup aswell. On Jan 7, 6:03 pm, Tiffany <[email protected]> wrote: > Our University is considering splitting up RedDot into two production > servers: one for editing and one for publishing. We are hoping that > splitting the two will help the system run smoother and quicker. We > have experienced problems with simultaneous multiple publications. > > Has anyone split their production up between editing and publishing? > What was your experience? Did you notice a significant increase in > performance? What was your process of splitting the two? What problems > did you encounter? > > Has anyone encountered issues with migrating the system to new > hardware? > > Thanks for your input!
-- 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.
