having issues with using formicaio in the chromebrowser since i pulled the latest version. the site opens but it doesn’t retrieve the data from the running nodes. In edge everything shows up perfectly. anyone else having this issue?
Did you try refreshing the page with Ctrl+F5 (clearing the cache)? Also, check the chome console with F12 and see if there is any error logged.
arg that did the trick indeed
@bochaco Just a quick question, are you depending on the RPC server here at all? (brilliant work here btw, loving seeing this)
It’s just I am keen to get nodes much more lean so rpc logging and metrics are things I am looking to minimise/remove if possible (well not all logging but where we calculate stuff to put in logs etc.)
It uses the metrics server only.
Metrics has been a great way to see how the node is doing. Please do not remove it.
SAME for logs.
If you want to reduce the load for production nodes, then please still have the build option to leave them in so some of us can build with the extended data being available.
I feel metrics are very good and helpful, but centralised collection of them is not a good look or feel moving forward.
Logs are a pet hate of mine. It’s not just the load they put on nodes, which is significant, it’s the security implications of them and also some logs actually calculate stuff, so they run wee programs if you like.
I keep saying to the guys, when you run a log you run a hobbled node. IMO Logging should only be a debug thing and never used in production secure networks. So fine for debug etc. but not for production.
I think we can reduce load on nodes by a significant amount if we just play is cool here and go for the smallest possible nodes e can get that are stable as hell, but absolutely tiny.
I may be outvoted, but I liked that about c++ at least, when you build in release it took all the logs out. That was a clever thing. I always feel Engineers want everything, RPC, logs, metrics and it leaves very little for actual logic in some ways
I was meaning for the node and on my machine/network to read, not a centralised collection.
As I suggested, at least keep them as a build option, not necessary for production please.
Updates are going smoothly. I’m running five instances of Formicaio on different kinds of systems from vps to old pcs.
Another thought I had was a shun threshold that would restart a node when it hits a certain number of shuns.
Thanks you again for all the effort.
Would that be of any help…? …I mean, wouldn’t it need to be killed/removed and a new one created with a fresh peer-id? I’m just thinking if the rest of the network will still have the peer-id shunned regardless you restarted it and/or see how many of them have previously shunned it and probably still do…?..
I did not think about it that deeply, but yes it would need to be killed restarted from scratch.
Which would mean Formicaio would have to know port numbers and port metric numbers for all nodes in use so it doesn’t try to restart the new node with current used ports.
I’m going to do a batch launch test today to see how it goes.
Is tht an Umbrel-only screen?
I am simply running the docker image in my usual Ubuntu docker setup and don’t see a screen like that.
No complaints about doing that way, but I think from this and an earlier post I may be missing some functionality by just using the docker image.
Also I would suggest that it is not the delay between creating nodes that is critical but the delay between starting them. 350 secs is a good safe delay IMHO for starting nodes. I found I could manually create say 10 nodes, start the first and then wait a few mins to hit the start button on each of the others. Perhaps the wording could be changed to reflect that?
As it should…
I’m running Umbrel in docker. It gives me an ip address I can access umbrelOS from.
Then open the app store, click in the upper right add community app store and enter the URL from the GitHub site GitHub - bochaco/formicaio: Le formiche sono insetti sociali che vivono in colonie e sono note per la loro organizzazione e cooperazione.
Which is this GitHub - bochaco/formicaio-app-store url
I then install Formicaio from the community app store and launch it which gives me a tab in my tab in my browser where I run the app and launch nodes and such.
This allows me to have one webpage on my PC where I can manage 5 instances of Formicaio.
Check at the README, if you used the docker compose
command described there to launch it, you will find the instructions to upgrade Formicaio without stopping your nodes, also by using a docker compose
cmd.
Yes, but since creating them all up front and then start them one by one with the delay doesn’t offer anything, I found it simpler to just create one by one, and apply auto-start to each of them along with the delay. Also, the batch can be cancelled at any time, in which case you won’t get any further nodes created when doing so.
Ah OK, I see the README has been updated since I last looked
bochaco has us covered in the latest version. I can check the auto start box which achieves the goal.
Im getting this when I try docker compose pull formicaio
willie@gagarin:~/projects/maidsafe/formicaio$ docker compose pull formicaio
no configuration file provided: not found
willie@gagarin:~/projects/maidsafe/formicaio$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
bc7f71c987c4 traktion/sn_httpd "sn_httpd_wrapper.sh…" 3 days ago Up 3 days 0.0.0.0:8080->8080/tcp angry_meninsky
089dcb1c952f bochaco/formicaio:latest "/app/formicaio" 2 weeks ago Up 2 weeks 0.0.0.0:52100->8080/tcp local-formicaio-1
2bcab76dd04b docker:27.2.0-dind "/entrypoint.sh dock…" 2 weeks ago Up 2 weeks
Is running the docker image without Umbrel deprecated now?
Still seems to be running fine - as it has done for the past few weeks
EDIT Wish list…
Sort nodes by port number, rewards, shunned count, records, connected peers.
Or I could try to work that out myself and send a PR. But that may take a while…
To run any docker-compose command you should be located at the path where the docker-compose.yml
file is, in your case move to the folder ~/projects/maidsafe/formicaio/deploy/local
and then try to run the docker compose pull formicaio
again.