Currently Docker-setup users won't have access to the Postgres database locally by default (even though the docker-compose setup may give a different impression), they will still use SQLite3 by default. In production (i.e.: Heroku) these users will probably use Postgres, so it's important to keep settings consistent everywhere.
Setting up the container and the volumes can be a bit tricky, so it's important to have this support out of the box.
We'll keep SQLite3 as an option for non-Docker users who don't want to spend much time configuring their databases for small projects, although it's highly recommended for everyone to use the Docker setup since it requires less configuring.
Motivation and Context
Screenshots (if appropriate):
Steps to reproduce (if appropriate):
Types of changes
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
[x] My code follows the code style of this project.
Description
Currently Docker-setup users won't have access to the Postgres database locally by default (even though the docker-compose setup may give a different impression), they will still use SQLite3 by default. In production (i.e.: Heroku) these users will probably use Postgres, so it's important to keep settings consistent everywhere.
Setting up the container and the volumes can be a bit tricky, so it's important to have this support out of the box.
We'll keep SQLite3 as an option for non-Docker users who don't want to spend much time configuring their databases for small projects, although it's highly recommended for everyone to use the Docker setup since it requires less configuring.
Motivation and Context
Screenshots (if appropriate):
Steps to reproduce (if appropriate):
Types of changes
Checklist: