It is a "production" system for my personal use :) The idea was to keep things as lightweight as possible, so I chose to use SQLite.
The only downside that I am aware of with SQLite is that there might be concurrency problems where there are a large number of transactions per second, but for my home document server I am unlikely to reach the limit. The SQLite documentation (http://www.sqlite.org/whentouse.html) says that it is ok for websites with up to 100,000 hits per day - although maybe not when using a Raspberry Pi and an SD card for storage. Jonathon. On Friday, 12 June 2015 03:39:58 UTC+12, Mark Phillips wrote: > > This is really great! > > Is your setup geared towards development or production? Your setup appears > to be using SQLite as the database, and I thought that was not recommended > for a production installation. > > Mark > > On Thu, Jun 11, 2015 at 6:23 AM, Gabriel Diteko <[email protected] > <javascript:>> wrote: > >> Brilliant! Thank you so much! You are a life saver! Though I'm using >> apache2 for deployment, these settings worked wonders for me. >> >> -- >> >> --- >> You received this message because you are subscribed to the Google Groups >> "Mayan EDMS" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- --- You received this message because you are subscribed to the Google Groups "Mayan EDMS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
