Adds two new bare metal bootstrap peers both with high end AMD cpus and 128GB ram. The first one is in the US and the second is in the EU. The second one is at an untested new provider.
* move to a message processor channel model for ceremony
* switch to goroutine
* readjust
* cut down volume
* keep distance data asserted
* bring it back so more bootstrap nodes can exist
* bump the version, it's go time
* Modify the wrong default volumes value to /root/.config (#109)
* move extract version logic to new version.go in config package
* update version extraction command
---------
Co-authored-by: talentbuilder <talentbuilder@163.com>
* experimental: switch mutex to RW to see if it alleviates backpressure on peer info
* relax mutex req
* reject unknown messages
* open the floodgates
* adjust message handler to use goroutine, i'll probably regret this
* switch that back, it was regret
* further discovery
* log more data
* forcibly block channel when unbounded
* else
* make it configurable so bootstrap peers are the only ones putting up with this.
* ok, non-starter, let's try a different route
* further tweaking
* let the peer info flow uninhibited
* final burn off on master
* final adjustments
* multi-stage Dockerfile
* add build arguments for git
* add taskfile
* switch back to copying source into build stage and clean up labels
* get image name from .env
* remove top level ARGs
* update DOCKER-README with Taskfile details
* mention light and safe image
* add a backup task
* add healthcheck
* add logs-folder task
* add warnings to backup task
* allow port overriding in docker compose
* Update README.md
Added link to Beginners' Guide to Setup a Node
* Added community section in readme.md
As discussed, added community section in readme.md and embedded the link to the detailed guide
