Update static assets packaging (so cmd/ageth/index.html ships as a part of ageth executable).
If you don't update index.html, you don't need to do this.
statik -src ./cmd/agethClean out all vestiges from previous ageth runs using local geths. If you're using local geths, these will be data directories, sockets, and keystores. If you're using remote geths, this is unnecessary.
rm -fr /tmp/ageth*Build everything.
make allRun ageth using stdin to provide an endpoint list definition.
printf './build/bin/geth\n./build/bin/geth\n./build/bin/geth\n./build/bin/geth\n./build/bin/geth\n./build/bin/geth' | ./build/bin/ageth > ageth.logRun ageth using a file from which to read newline-delimited endpoint definitions.
./build/bin/ageth -f fake-endpoints.txt > ageth.log
This example redirects ageth's stdout to a logfile. If ageth is running local geths, these logs
will be the aggregated logs of all the geths she's running.
If ageth is using remote geths, this is unnecessary; she doesn't have access to remote logs and her stdout will be empty.
- TODO: Handle log placement better. The test
scenarioswill produce their own logs/reports, which probably should go to stdout. This will collide with the local geth logs, if any.
First: It's a little obtuse, but endpoints can either be
ws://endpoints (websockets), OR./build/bin/geth"endpoints".
This is where the scare-quotes come in.
If the value doesn't have a valid URL scheme, she'll consider it as a path to a local geth exectuable. She'll attempt to start it, and connect over IPC.
If, on the other hand, the value does have valid URL scheme, she'll just connect with it by dialing the RPC URL.
If remote, the endpoint MUST be a ws:// (websocket) URL. ageth needs a websocket so she can subscribe to the node's head events.
ageth eats "endpoints" for geths, and
- if they're local, she can turn them on and aggregate their logs
- if they're remote, she'll just wrap them up in RPC clients and connections
An endpoint file may looks as follows. This will yield an ageth managing 4 remote nodes and 2 local ones.
ws://somewhere.com:8546
ws://somewhereelse.com:8546
ws://wherethough.com:8546
ws://anywhere.com:8546
./build/bin/geth
./build/bin/gethAs above, if you have this ☝️ in a file ageth-endpoints.txt, you'll use:
./build/bin/ageth -f ageth-endpoints.txtOR
cat ageth-endpoints.txt | ./build/bin/agethThe "Scenario" interface is defined as
type scenario func(nodes *agethSet)
You write these, and then add them to the root scenario loop:
for {
for i, s := range []scenario{
scenario5,
}{
log.Info("Running scenario", "index", i)
globalTick = 0
s(world)
}
}An example scenario using this pattern is provided in ./cmd/ageth/cmd/scenario_5.go.
From startup, ageth hosts an "Observer" website at :8008.