You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've discussed in the past how it can be a bit inconvenient how to handle the URLs/subdomains one need for the real database and the index meta-db to participate in providers.json. Typically we do something like: https://optimade-index.example.org.
An alternative, which I don't think anyone uses, is to use a place under extensions, i.e., something like this:
https://optimade.example.org/extensions/indexdb
However, it looks a bit confusing, since this is a whole other OPTIMADE endpoint and not an "extension".
So, I want to suggest: would it make sense to completely reserve another URL under the base URL specifically for this use? I.e., something like:
<base url>/indexdb
Which is reserved to allow providers to OPTIONALLY use to host an index database base url. (But, the point being, you are allowed to provide it somewhere else - in some setups it is easier to provide it under its own subdomain; client MUST NOT assume there is an index meta-db there).
The text was updated successfully, but these errors were encountered:
I really like this idea! Would greatly simplify the case of providing a single API, and optimade-python-tools can serve it from one app and include it when configured (which would avoid the need for some of the netlify providers list providers)
We've discussed in the past how it can be a bit inconvenient how to handle the URLs/subdomains one need for the real database and the index meta-db to participate in
providers.json
. Typically we do something like:https://optimade-index.example.org
.An alternative, which I don't think anyone uses, is to use a place under
extensions
, i.e., something like this:However, it looks a bit confusing, since this is a whole other OPTIMADE endpoint and not an "extension".
So, I want to suggest: would it make sense to completely reserve another URL under the base URL specifically for this use? I.e., something like:
Which is reserved to allow providers to OPTIONALLY use to host an index database base url. (But, the point being, you are allowed to provide it somewhere else - in some setups it is easier to provide it under its own subdomain; client MUST NOT assume there is an index meta-db there).
The text was updated successfully, but these errors were encountered: