38 lines
1.2 KiB
Markdown
38 lines
1.2 KiB
Markdown
|
There are 3 tools;
|
||
|
|
|
||
|
|
1. fetcher
|
||
|
|
2. processor
|
||
|
|
3. strengthen-trust
|
||
|
|
|
||
|
|
For ease of use, the order of usage is also alphabetical order.
|
||
|
|
|
||
|
|
You have two directories;
|
||
|
|
one is the input directory where we store temporary files,
|
||
|
|
where you can drop config files and the like.
|
||
|
|
We call that IN_DIR
|
||
|
|
|
||
|
|
Then there is the webserver directory, something you can point your
|
||
|
|
webserver directly to with the html files and images that are served.
|
||
|
|
WE call that OUT_DIR
|
||
|
|
|
||
|
|
1. fetcher IN_DIR
|
||
|
|
|
||
|
|
Will connect to a Hub and download any bcmr referring transactions.
|
||
|
|
This application never returns as it keeps on listening for new blocks,
|
||
|
|
you can harmlessly interrupt it at any time.
|
||
|
|
|
||
|
|
2. processor IN_DIR OUT_DIR
|
||
|
|
|
||
|
|
This parses the transactions and downloads any missing files (jsons and images)
|
||
|
|
It also generates the html and json files in the output.
|
||
|
|
|
||
|
|
3. strengthen-trust IN_DIR
|
||
|
|
|
||
|
|
This connects to a Hub and the indexer in order to complete auth-chains by
|
||
|
|
downloading any missing transactions.
|
||
|
|
This step is optional, but without it your generated pages will not be able
|
||
|
|
to record higher trust to bcmrs that refer to an authchain if the authchain
|
||
|
|
itself refers back to that bcmr.
|
||
|
|
|
||
|
|
4. If 3 ran, run step 2 again to update any category files with higher trust.
|