-
Notifications
You must be signed in to change notification settings - Fork 129
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
SQLIte deployment? #307
Comments
@thomascube That note essentially is present since the beginning of this repository (3cd4286). Can you recall the reasons for it? And/or do you still think that statement is correct and required? (From my point of view, sqlite might not be suitable for bigger setups, but for smaller ones if might be fine in production, too. So I'd just remove the last sentence from that paragraph.) |
Indeed this was probably the reason for this sentence. Because sqlite ist file based, when multiple (PHP) processes (e.g. multiple users/sessions) want to access the database, locking may delay the access leading to bad performance. Maybe we can just rephrase this accordingly. |
@thomascube: Yes, that seems much more appropriate Thanks all. |
Can anyone clarify please?
"By default, the image will use a local SQLite database for storing user account metadata. It'll be created inside the container directory /var/roundcube/db. In order to persist the database, a volume mount should be added to this path. Please note that this option should not be used for production environments."
(SQLite) should not be used for production environments
It would be good to know why SQLite is not recommended for production deployment.
The text was updated successfully, but these errors were encountered: