tdm:master
from tdm:mapping-tools-use-env-url
on 23 Jan 2023
loterre-resolvers/v1/9SD/expand.ini |
---|
loterre-resolvers/v1/9SD/identify.ini |
---|
loterre-resolvers/v1/D63/expand.ini |
---|
loterre-resolvers/v1/D63/identify.ini |
---|
loterre-resolvers/v1/P66/expand.ini |
---|
loterre-resolvers/v1/P66/identify.ini |
---|
mapping-tools/README.md |
---|
mapping-tools/v1/apc/2018/doi.ini |
---|
mapping-tools/v1/halAuthorId/idRef/json.ini |
---|
mapping-tools/v1/homogenize/documentType/json.ini |
---|
mapping-tools/v1/homogenize/publisher/json.ini |
---|
mapping-tools/v1/homogenize/source/json.ini |
---|
mapping-tools/v1/idRef/orcid/json.ini |
---|
mapping-tools/v1/inspire-category/meta-category/json.ini |
---|
mapping-tools/v1/inspire-labos/in2p3-labos/json.ini |
---|
mapping-tools/v1/rnsr/instituts-cnrs/json.ini |
---|
As the mapping tables are now external to the mapping-tools lodex-workers instance, it would be useful to set the URL of the tables server in the instance's configuration.
Thus, the creation of an environment variable named
TABLE_SERVER_URL
.Oh: when you change
TABLE_SERVER_URL
, you have to rm/tmp/memory
directory, where cache is stored, otherwise new tables won't be taken into account.Maybe we should add a
/v1/clean-cache
route ?feat(mapping-tools): Add TABLE_SERVER_URL environment variable
d44a7d6
intomaster
frommapping-tools-use-env-url
on 23 Jan 2023mapping-tools-use-env-url
branch on 23 Jan 2023