• Every repository on this subject

TLDR

MAIN_ADDRESS=... rss=1, bit=1, jvc=1, ch4=1, for=1, hac=1, mas=1, nos=1, a7d=1, ap9=1, lem=1, wei=1, fol=1, you=1, tra=1 docker compose -f spotters.yaml -f docker-compose.yaml up -d

Where each three letter code represent a spotter module ;

⚠️ There is automatic orchestration of spotters atm, configuration is completely left to you.

📘 How to mine EXD

The client is ran using two docker compose files.

• docker-compose.yaml : processing and web3
• spotters.yaml : scraping services

1️⃣ Core

image	Image size	description	Version	Pulls
transactioneer		Web3 interaction
bpipe		Batch processing
upipe		Unit processing
orchestrator		Orchestration & Monitoring

• MAIN_ADDRESS is specified as an ENV variable

Example

MAIN_ADDRESS=... docker compose up -d

more parameters to buff the perf

2️⃣ Spotters

• Every available spot driver repositories

image	Image size	Version	Pulls
spotseekingalphad89ba32s
spotbitcointalk4de40ec26
spotjvc8439846094ced03ff
spotrss007d0675444aa13fc
spotch4875eda56be56000ac
spotforocoches86019fc2d4
spothackbc9419ab11eebe56
spotmasto65ezfd86424f69a
spotnostr5fa856e7234fbee
spota7df32de3a60dfdb7a0b
spotap98j3envoubi3fco1kc
spotlemmyw04b6eb792ca4a1
spotwei223be19ab11e891bo
spotfollowinc645fc950d7f
spotyoutube00e1f862e5eff
spottradview251ae30a11ee

spotters.yaml provides an easy way to launch the different spotters with different redundancy parameters, each module is parametrable with it's three first leters (jumping over spot)

Example

rss=2 docker compose up -d -f spotters.yaml

Will launch two rss instances.

⚠️ Important

• There is no orchestration mechanism when you launch your spotters this way.
• They will be staticly launched and the module distribution usage is 100% under your control.