Hi Sean, You are right, uploaded files will be a problem. I'm not aware of a solution that does not require new code, except for something like NFS.
Another thing to watch out for is the search index. Roller uses Lucene directly, which means each instance of Roller will have it's own Lucene index. As bloggers make changes to posts, indexes may get out of sync and search will not work uniformly. You could work around this by re-indexing each Roller instance periodically. But, unfortunately, I don't think there is a way to trigger a re-index of the Roller search index, except for stopping Roller, deleting the search index directory then restarting Roller -- Roller will re-index all blog entries if no index data is found. Another work around is to just use Google for your site search. Hope that helps. - Dave On Tue, May 26, 2015 at 10:15 AM Sean Pritchard <spritch...@militaryhire.com> wrote: > Hi, > > I'd like to use roller in an autoscaled AWS cluster. It looks like the > main hurdle to doing that will be the local media directory that contains > uploaded images. Have any of you tried running roller in such an > environment? Are there alternatives to storing the media files in local > storage? For example in AWS S3? Are you aware of any other factors that > may interfere with running roller in a active-active loadbalanced cluster? > > Best Regards > Sean > MilitaryHire - Jobs for Veterans > https://www.militaryhire.com >
