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
This repository comes without documentation, and as such without build instructions.
Assuming this was part of the NGI0 work, it would be nice to be able to find little breadcrumbs that direct a curious visitor to instructions on how to build and run this software.
The database and the SDK part of the project are open-source and include their documentation.
Unfortunately I am unable to find that documentation. Are there plans to provide usable documentation alongside this publicly funded open source platform?
In an ideal world, the whole build and run procedure is abstracted into Containerfiles and a Compose example.
In a even more ideal world, the Containerfiles are continuously integrated into OCI images and pushed to a publicly accessible OCI registry, suitable for reuse by the public elsewhere.
The text was updated successfully, but these errors were encountered:
Hi we are working on a containerised version of the platform - this is however pushed on our roadmap to 2024 - for now the best repo to start is https://github.com/atelier-saulx/selva this is the code name for the database component of based
This repository comes without documentation, and as such without build instructions.
Assuming this was part of the NGI0 work, it would be nice to be able to find little breadcrumbs that direct a curious visitor to instructions on how to build and run this software.
The site reads:
Unfortunately I am unable to find that documentation. Are there plans to provide usable documentation alongside this publicly funded open source platform?
In an ideal world, the whole build and run procedure is abstracted into Containerfiles and a Compose example.
In a even more ideal world, the Containerfiles are continuously integrated into OCI images and pushed to a publicly accessible OCI registry, suitable for reuse by the public elsewhere.
The text was updated successfully, but these errors were encountered: