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
Our team is interested in self-hosting DataFed metadata services—having hosted several DataFed repositories for some time, but always relying on ORNL-provided metadata services.
The documentation on the compose dev environment is not quite at a point where we feel able to follow it for a metadata services deployment. In particular, it isn't clear what the prerequisites are, or how it might look to have both repository and metadata services running on one server—assuming that's even possible. What does the target setup look like?
Acceptance Criteria
We would like to see the documentation fleshed out such that a team like ours could follow it to complete a metadata services deployment without further assistance.
We are happy to help revise and expand the docs, once we know what the relevant details are. Perhaps if we had a meeting with one or more members of the DataFed team to help us go through the deployment process, we could take notes and transfer that into clearer documentation to help others.
The text was updated successfully, but these errors were encountered:
AronPerez
changed the title
Docs for self-hosting metadata services
[Docs] Self-hosting Metadata Services
Apr 30, 2025
Description
Our team is interested in self-hosting DataFed metadata services—having hosted several DataFed repositories for some time, but always relying on ORNL-provided metadata services.
The documentation on the compose dev environment is not quite at a point where we feel able to follow it for a metadata services deployment. In particular, it isn't clear what the prerequisites are, or how it might look to have both repository and metadata services running on one server—assuming that's even possible. What does the target setup look like?
Acceptance Criteria
We would like to see the documentation fleshed out such that a team like ours could follow it to complete a metadata services deployment without further assistance.
We are happy to help revise and expand the docs, once we know what the relevant details are. Perhaps if we had a meeting with one or more members of the DataFed team to help us go through the deployment process, we could take notes and transfer that into clearer documentation to help others.
The text was updated successfully, but these errors were encountered: