Monero public node aggregator.
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
Go to file
lza_menace 5d363417f8 more improvements to map load performance 4 weeks ago
conf adjust tor config 1 year ago
xmrnodes more improvements to map load performance 4 weeks ago
.dockerignore removing some things from docker context 1 year ago
.gitignore add mirror to monero infodump site 1 year ago
Dockerfile-i2p i2p integration (#26) 1 year ago
Dockerfile-tor i2p integration (#26) 1 year ago
LICENSE Initial commit 4 years ago
Makefile update docs, remove bin, fix ux on no data 1 year ago
README.md update deps 9 months ago
crontab fix path 1 month ago
docker-compose.yaml setup logging config 1 year ago
env-example update docs, remove bin, fix ux on no data 1 year ago
manage.sh add onion script and update mgmt script 9 months ago
migrate_schema.sh add simple schema migration script 1 year ago
onion.sh add onion script and update mgmt script 9 months ago
requirements.txt update deps 9 months ago
scrape.py split resources out 1 year ago

README.md

monero.fail

Monero node tracker.

Stores Monero (and Wownero) nodes for clearnet, Tor, and I2P.

Setup

Tools you will need:

  • Docker # apt-get install docker.io
  • docker-compose # apt-get install docker-compose
  • python3 (linux os will have this)
  • python3-venv # apt-get install python3-venv

Development

I have provided a Makefile with some helpful stuff...make sure to install make to use it.

The map portion of the service requires the GeoLite2 db...the make setup command fetches a copy via wget.

# install python virtual environment and install application dependencies
make setup

# default configs work out of the box, modify .env if needed
# setup .env
cp env-example .env
vim .env

# run services (tor, i2p, etc)
make up

# run development server
make dev

# access at http://127.0.0.1:5000

Background Tasks

There are 3 things that need to run in the background:

  • validating nodes that have been added
  • checking existing node health
  • scraping peer lists

I accomplish this via crontab and some management scripts. Ensure the i2p and tor containers are running (or just on the host) so that requests can be proxied.

docker-compose up -d
./manage.sh validate
./manage.sh check
./manage.sh get_peers

Production

For production, update SERVER_NAME in .env to your production URL/domain. Use manage.sh (or provided Makefile) to serve the Flask process using Gunicorn.

./manage.sh prod

Runs the Gunicorn process on port 4000. Setup a web server to proxy requests to that port.

Kill production Gunicorn with make kill.