remote: -----> No change in requirements detected, installing from cache
remote: -----> Installing pip 20.1.1, setuptools 47.1.1 and wheel 0.34.2
remote: -----> Installing SQLite3
remote: -----> Installing requirements with pip
remote: -----> pgbouncer app detected
remote: Using pgbouncer version: 1.14.0
I’m wondering about the third line there because my Django project is already configured with a PostgreSQL db populated with some data. When I navigate to my web app, the PostreSQL db data is still being served (which is what I actually prefer). So does this mean that the buildpack output about SQLite3 is inaccurate? Was SQLite installed or not?
Thank you, KenWhitesell, for your help and guidance so far.
I need SQLite for testing locally and Postgres for my project deployed on Heroku. So I need both. My next step is to declare both configuration variables in separate settings.py, one settings.py for testing locally and one for production remotely. I have already begun working on that as described in Casey Faist’s tutorial: From Project to Productionized with Python | Heroku
Looking at the docs for dj_database_url, it looks like the DATABASES line should be the only one you need. If it’s failing in your local dev environment, then I would assume that it’s because you’re not setting your environment variables correctly.
I’m saying that the referenced documentation is saying that that’s all that is necessary.
I don’t believe I’ve said anything about those two lines - that’s what you’ve reported in your other post as a solution to a different problem.
You have not posted a KeyError message in this thread. I’m going to assume you’re referring to this snippet:
See the referenced docs for dj_database_url for the environment requirement (DATABASE_URL) for using the .config method. Verify that that settings has been made and is correct for your local dev environment.