New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use something other then sqlite #20
Comments
Would work fine while the database is small and uncomplicated. I actually run bull, my digital sales app for selling my book, with sqlite as it simplifies things for small databases. That being said, if you want to change the DB engine, you're welcome to send a pull request :) |
Out of curiosity how is this app deployed? On Tue, Mar 11, 2014 at 11:14 AM, Jeff Knupp notifications@github.comwrote:
|
The contents are copied to a certain directory (/srv/www/bull) and the app is run via |
Are you running multiple workers? I guess I am wondering how sqlite3 does On Tue, Mar 11, 2014 at 11:30 AM, Jeff Knupp notifications@github.comwrote:
|
SQLite can certainly handle the level of concurrency I require. I just run On Tue, Mar 11, 2014 at 2:33 PM, Alex Kessinger notifications@github.comwrote:
|
It's great for development, but when you actually deploy probably won't work, right?
The text was updated successfully, but these errors were encountered: