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

Does the addition of an email address for CrossRef consolidation require to rebuild the Docker container? #634

Closed
davidefiocco opened this issue Sep 4, 2020 · 3 comments

Comments

@davidefiocco
Copy link

I am using GROBID on Docker https://grobid.readthedocs.io/en/latest/Grobid-docker/ and thought to use CrossRef consolidation, doing that in the "polite" way, thus specifying a value for the mailto value in grobid-home/config/grobid.properties (which is a very trivial change).

To do so, do I need to rebuild a custom Docker image, or do I have the option to pass the email address to be used in the CrossRef calls to the container pulled from the public image on Docker Hub e.g. with an option in

docker run -t --rm --init -p 8080:8070 -p 8081:8071 lfoppiano/grobid:${latest_grobid_version}

?

@lfoppiano
Copy link
Collaborator

Hi @davidefiocco,
in theory you can use the environment variables as explained here: #482

to overwrite the property you want in the grobid.properties.

export ORG__GROBID__CROSSREF__MAILTO=youremail

should do the trick.

@davidefiocco
Copy link
Author

davidefiocco commented Sep 4, 2020

OK @lfoppiano thanks a million, I will try! By that reasoning, would

docker run -t --rm --init -p 8080:8070 -p 8081:8071 --env ORG__GROBID__CROSSREF__MAILTO='myemail' lfoppiano/grobid:${latest_grobid_version}

also do? That would be super handy also considering #628

@lfoppiano
Copy link
Collaborator

Yes. As mentioned in the documentation https://grobid.readthedocs.io/en/latest/Grobid-docker/#configuration-using-environment-variables

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

2 participants