Re: Deploying few Piers - options

At 11:03 02/05/2011, Davorin Rusevljan wrote: Nothing special to report, as far as I can remember now, but does not means zero risk. Basically, the (Debian) server contains: - one image and associated files, including the 'files' folder. - several virtual host configurations, one per distribution (in my configurations), which redirect http requests to the corresponding seaside/pier distribution/application. The image is automatically saved, each time one of the distributions is modified. This works technically fine, but the risk is to save your image with corrupted objects. For example, I had troubles with the search widget (on pages that contain text copied from a word document). All in all, AFAIK, this method is less frequently used for deploying Pier distributions. So, I'd recommend the follwoings: - double check some critical routines, including persistence, - configure both your server and image for a remote (emergency) access via VNC, and - backup regularly your image + files Hoping this helps, Cheers, Reza