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
{{ message }}
This repository has been archived by the owner on Sep 24, 2019. It is now read-only.
demo.openbel.org should be a landing page that has a link to belmgr, apidocs, openbelapi (and any other services available to demo by openbel). the links to each service can be either subdomains or paths off of demo.openbel.org (same for dev.openbel.org below))
dev.openbel.org should be a landing page that has all of the endpoints for the dev version of the belmgr, openbelapi, apidocs, etc
openbel.org should be the landing page for openbel and point to the other resources as a high level guide
api.openbel.org should be the public production endpoint for the openbel api
apidocs.openbel.org should be the public production endpoint for the openbel api - in case we decide to use a hosting service for this
auth.openbel.org (or users.openbel.org) for the authentication endpoint
belmgr.openbel.org should be the public production belmgr instance
We'll retire the belframework.org domain completely.
For the internal Selventa installation of openbel tools/services - belmgr.selventa.com, openbel.selventa.com(/api?) - apidocs hosted on public server and linked from top-level api entrypoint.
The text was updated successfully, but these errors were encountered:
Proposing:
demo.openbel.org should be a landing page that has a link to belmgr, apidocs, openbelapi (and any other services available to demo by openbel). the links to each service can be either subdomains or paths off of demo.openbel.org (same for dev.openbel.org below))
dev.openbel.org should be a landing page that has all of the endpoints for the dev version of the belmgr, openbelapi, apidocs, etc
openbel.org should be the landing page for openbel and point to the other resources as a high level guide
api.openbel.org should be the public production endpoint for the openbel api
apidocs.openbel.org should be the public production endpoint for the openbel api - in case we decide to use a hosting service for this
auth.openbel.org (or users.openbel.org) for the authentication endpoint
belmgr.openbel.org should be the public production belmgr instance
We'll retire the belframework.org domain completely.
For the internal Selventa installation of openbel tools/services - belmgr.selventa.com, openbel.selventa.com(/api?) - apidocs hosted on public server and linked from top-level api entrypoint.
The text was updated successfully, but these errors were encountered: