-
Notifications
You must be signed in to change notification settings - Fork 1
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
Configure Endpoints #15
Comments
DAM uses 'OKFGR_TS' env variable to configure the greek server, and it calls the package okfgr_dm, see here, https://github.com/openbudgets/okfgr_dm/blob/master/okfgr_dm/okfgr_server.py does this help? |
@skarampatakis on our side, it works by updating the configuration in the .env file. |
On which .env you mean? This is the .env on Fhg server on the docker-config/damapp folder
However when used through Indigo it sends a request to http://apps.openbudgets.eu/ocpu/ocpu/library/DescriptiveStats.OBeu/R/open_spending.ds/print so I think it is not respected or it is a different file? |
@skarampatakis you are right. something @liyakun knows better |
@skarampatakis @HimmelStein I tried to change the .env file, but it seems that it is not used, I have to change dam.json to make it call the opencpu running on FHG server. |
So it is not the .env file who defines this parameter but the dam.json? Are these parameters required somewhere else? Otherwise please remove them to prevent confusion later on. In terms of integration then it seems that we could have a dam.json file on the docker-config/damapp folder and copy it on build. But please take care that it should also be somehow configurable (domain agnostic) as required by openbudgets/integration@a04eeb3#commitcomment-24646654 |
It seems that the env variables are not respected anywhere.
I have set the .env to get the opencpu endpoint from my local container but it consists to ask the remote.
Then I saw this file
https://github.com/openbudgets/DAM/blob/staging_indigo/tasks/dam.json
Is it here where I need to change the parameters?
The text was updated successfully, but these errors were encountered: