On Mon, 26 Nov 2012 16:06:31 +0200 Zeev Pekar <[email protected]> wrote:
> Hi, > > I'm considering droping Drupal and move to using fossil also as a CMS. I've done some experimenting with this idea. In my mind the jury is still out. One problem is images. Most browsers will make potentially many simultaneous connections to fetch all the images on a page at the same time (think: often images/adds are actually on different severs anyway). Where as a normally loaded fossil site might not get hit with problems relating to sqlite database lock contention, this scenario I found could. One work around is storing images not in the scm files, but "passing through" with the doc hosting mechanism. Storing a static site in fossil scm of course works - i.e. exporting the files to a server root. So maybe there is good strategy to run a script to export files from the scm database to a doc folder or something. -- C. Thomas Stover Stover Enterprises, LLC _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
