Skip to content
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

.env is not considered #107

Open
BPMCRA opened this issue Jun 28, 2023 · 3 comments
Open

.env is not considered #107

BPMCRA opened this issue Jun 28, 2023 · 3 comments

Comments

@BPMCRA
Copy link

BPMCRA commented Jun 28, 2023

My file /etc/ckan/datapusher-plus/.env is not considered.
I had to edit /usr/lib/ckan/dpplus_venv/lib/python3.8/site-packages/datapusher/config.py so that datapusher can push a more big file than 25 Mo and connect to my datastore database.

Ubuntu 22.04
Production installation.

@jqnatividad
Copy link
Contributor

Hmmm... The .env file will need to be in the current working directory of the program for it to be considered.

Can you try moving the .env file to the /usr/lib/ckan/dpplus_venv/bin directory?

@D-Simona-G
Copy link

D-Simona-G commented Jul 7, 2023

I have the same problem but with the Dockerised version. Weirdly enough, the
SQLALCHEMY_DATABASE_URI vars from the same env file is considered, the rest are just ignored and using defaults instead.
It does not connect to the datastore on the URL provided through .env. Still tries to use localhost:5432, but writes to datapusher_jobs table just fine.

@Slhoka
Copy link

Slhoka commented Jul 27, 2023

Same here for me with the Dockerised version.
I try to only use variable from my docker-compose.yml however the values from WRITE_ENGINE_URL and SQLALCHEMY_DATABASE_URI (for exemple) comes from the .env that I need to package inside the image and which is located in /etc/ckan/datapusher

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants