Basic ScienceMesh services
How a Reva IOP site should be configured to provide a minimal set of services required for joining the Science Mesh.
To get an understanding on how to create, use and manage your two Reva configurations, please refer to the official Reva documentation.
NOTE: The following configuration sections are meant to be put into the main Reva configuration file (
revad.toml
), unless explicitly stated otherwise.
IMPORTANT: values marked with
$...$
are meant to be changed to something more meaningful
If you are joining the ScienceMesh with an ownCloud “OCIS” system, then follow the instructions below.
If you are joining with an ownCloud 10 or Nextcloud system then you can also use the sciencemesh1.toml, sciencemesh2.toml, and sciencemesh3.toml for your three required revad processes. Make sure to replace all your.revad.com
, your.revad.ssl
, and your.efss.com
strings in each of them with your actual revad and efss host names!
your.revad.com
with your revad internet-facing hostnameyour.effs.com
with your Nextcloud/ownCloud internet-facing hostnameyour EFSS name
with a human-readable name for Nextcloud/ownCloud instance../reva/cmd/revad/revad --dev-dir .
- a Helm chart for running the three revad processes will hopefully be available soon!How a Reva IOP site should be configured to provide a minimal set of services required for joining the Science Mesh.
ADDON: How to configure your IOP site to host a Mesh Directory service.
ADDON: How to configure your IOP site to share access to some CS3MESH-compatible collaborative applications
ADDON: How to integrate your IOP deployment with the Nextcloud or OwnCloud EFSS solutions.
Here you can find an example of toml file needed to set up all necessary services for your reva instance. It consists of the services described in the others Configuration sections. This toml file is used for REVA deployment and referenced there as standalone.toml
.