Am 29.04.2011 um 16:50 schrieb Davorin Rusevljan: If you are talking about low traffic this sounds like multiple kernels in one image is the easiest to do. You don't have multiple piers or pier distributions but multiple kernels that are attached two different paths via PRPierFrame. That is really easy to do and fast enough. Norbert

Am 01.05.2011 um 17:46 schrieb Reza Razavi: Calling register this way is not advizable. As you can see it does 'PRKernel reset'. This will empty the instances on the PRKernel class side. You will end up having multiple kernels attached to PRPierframes as handler but only the last one will be attached to the instances of PRKernel. You're not able to e.g. select it from the configuration panel in seaside anymore. Using it without the reset is indeed a good idea. About the "files" folder. Pier uses Magritte and Magrittes MAExternalFileModel has a class side setting for the directory and path to use. So you are right, having all kernels in the same image means to share all files in the filesystem within the same directory. But I don't think this is a problem. You can easily divide them afterwards by having a visitor collecting the files for each kernel. I did this in my gemstone pier exporter utility: http://norbert.hartl.name/blog/pier-export-import-util-for-gemstone/ . Norbert

Thanks for all inputs! Are there any unexpected repercussions on persistence that I need to worry about? (I use ImageBased persistence currently) Davorin Rusevljan http://www.cloud208.com/

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