Skip to content

Postgres over Sqlite #11

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

Open
MayMeow opened this issue Oct 26, 2022 · 0 comments
Open

Postgres over Sqlite #11

MayMeow opened this issue Oct 26, 2022 · 0 comments
Labels
🤷‍♀️needs to be decided Not decided in given problem 🙏 help wanted Extra attention is needed ❓ question Further information is requested

Comments

@MayMeow
Copy link
Owner

MayMeow commented Oct 26, 2022

A few commits back I switched to using SQLite database because application development with it is much easier (you don't need any additional server) Eventually, however, I will go back to Postgres, mainly for the following reason:

The application for production environment is built on CI and the user is set to www-data which causes a problem with access rights to the database file.

I find that it is probably easier to add another database service to the docker-compose subfile than to create a new folder for database and set access rights on each installation.

The lines above were against using sqlite

The reason for using sqlite is that I don't plan to use this application for a large number of visitors on a regular basis (my blog has about 100 visitors a month). Also the database backup is easier.

@MayMeow MayMeow added 🙏 help wanted Extra attention is needed ❓ question Further information is requested 🤷‍♀️needs to be decided Not decided in given problem labels Oct 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🤷‍♀️needs to be decided Not decided in given problem 🙏 help wanted Extra attention is needed ❓ question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant