hashfriend
commented
3 months ago I see that docs are getting scattered in folders and subfolders and important infio buried within threads in Discord. Why not update the actual readme and docs folder? I do not have time to hang out in all your channels for info which should be part of a single page doc.
Is /docs the most up to date documentation to get the node running, or is it /deployment? Or is it somewhere in the Discord threads? Or on docs.oceanprotocol.com which surprisingly has no mention of how to run a node whatsoever? Main readme does not mention anything for /deployment and for proper DX following existing project structure this folder should not exist. /script and /docs are already there, now you mix it up in a new /deployment folder. What else you expect developers to do apart from deployment that it justifies its own folder adding to the confusion?
Teams with a way lower market cap do it like this and do not require their community to hunt for information in multiple folders & files. One single source of information. I am sure your UX people can help you with that https://docs.streamr.network/guides/how-to-run-streamr-node/
As for deployment script, new questions and findings:
- What's the "Ocean Node admin account"? If I add my private key whuy do I need to add public key as you should be able to derive it from private key. So this suggests private key account and "Ocean Node admin account" should be different?
- the actual start command, which is nowhere mentioned in the docs but only printed out by the script in the end, should be
docker compose up -dand NOTdocker-compose up -d
Regardless, when following the rest of /docs after following the script in /deployment, I can't get info out of my node either:
$ curl http://localhost:8000/getP2pPeer?peerId=16Uiu2HAkwWe6BFQXZWg6zE9X7ExynvXEe9BRTR5Wn3udNs7JpUDx
nullAlso not showing up on nodes.oceanprotocol.com which is a resource not mentioned at all in any of the multiple places you call docs. I guess I need to read 100 messages in multiple Discord threads to get info to run a node. Highly frustrating, especially considering I was trying to run a node before you even announced it but because of missing and confusing docs my node was not reachable as it seems and despite reporting in here nobody answered
update: got it working after investing another hour by ignoring the main readme, nuking everything and starting with the new install script. Figured nodes.oceanprotocol.com is not searchable by IP address. My node is now showing up but out of the box indexer is still not running. In the indexer section on my dashboard I see
Indexing queue is empty.
Node is not running Indexer. No need to get queue at this point!Which probably is caused by:
error: CONFIG: ❌ INDEXER_NETWORKS is an empty array, Running node without the Indexer component...Yet by default this env var is not set in what is advertised as the recommended way to run a node. Also INDEXER_NETWORKS is not documented anywhere. Is running indexer required for incentives eligibility?
Additionally, none of the test commands listed in the networking docs are working, they all return null
As for nodes.oceanprotocol.com, my node's data has not moved for multiple days, and is still showing older version despite multiple version updates.
Sorry for random reporting but have some errors shown in logs when starting up, think needs more docs on required env vars in combination with type of deployment. Docs say Docker is prefered and
PRIVATE_KEYis only required env var, but in env var docs more env vars are said to be set if using Docker. So which ones?For reference, running on Ubuntu 22.04 with Docker, all in default state with latest apt update and some basic server hardening. This also includes running
ufwas firewall.Starting all up with:
First error I ghet is because of missing
RPCSenv var, preventing indexer from running:So suppose
RPCSis required? So which networks are required then?As for those warnings:
Using defaults when env vars are not set probably should not trigger a warning (only log level?) but mayvbe that's just me. As far as I see all seems fine despite them not set?
I then tried to check if node is available following networking docs but have no success. I tried to run on server:
and get
And from outside:
But can't get it to connect to anything. Is this expected and is my node still accessbile by other peers?
Firewall is setup like so:
Any more ports I should open?
In the end I see stuff like this so it looks like all is running fine?
Finally as for system requirements, seeing that readme now says "latest iOS". As there is no way to have any process of any app running on iOS indefinetly in the background, this seems like a wrong suggestion. I don't see how any mobile OS could be used as an always online network node unless with a custom rooted ROM. Am I missing something?