The fact that we have a hyperlink to the GraphDB website as one of the first things on the deployment docs is still prompting some users to install the app directly from the website (despite our note not to do so), which creates problems for our Docker Compose deployment recipe b/c there is now an existing GraphDB instance (that doesn't participate in the network with the other tools). This becomes very confusing to debug later on.
To remedy this, we should make the preamble super simple (if we keep it at all) to just briefly introduce that we are using a RDF triple store backend, with a big warning to not download/install GraphDB manually.
Description
The fact that we have a hyperlink to the GraphDB website as one of the first things on the deployment docs is still prompting some users to install the app directly from the website (despite our note not to do so), which creates problems for our Docker Compose deployment recipe b/c there is now an existing GraphDB instance (that doesn't participate in the network with the other tools). This becomes very confusing to debug later on.
To remedy this, we should make the preamble super simple (if we keep it at all) to just briefly introduce that we are using a RDF triple store backend, with a big warning to not download/install GraphDB manually.
Relevant documentation pages
No response
Additional details
No response