serve: prepare api, handle custom prefixes, external MongoDB
#81
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ml-evs
approved these changes
Aug 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR improves
optimake serveto allow to prepare/set up a production API byWhat needed special care was the case where the custom provider prefix does not match with the one specified in the JSONL. In this case, the prefix needs to be updated in the property definitions. In principle, this could potentially be moved to the optimade-python-tools, as it already contains the mongodb injection script. Currently I need to populate the e.g. the MongoMock in a slightly hacky way (by importing the o-p-t to start the MongoMock and then accessing it directly).