Documentation for Boost v2 (LID information)

[nonsense]

1. • Document LID architecture- https://boost.filecoin.io/experimental-features/local-index-directory
2. • Document LID requirements - https://boost.filecoin.io/experimental-features/local-index-directory/requirements
3. • Document LID migration - https://boost.filecoin.io/experimental-features/local-index-directory/initialisation
     • Complete sections about migration
     • Guidance (if we want to provide any) on deals to potentially skip
4. • Add variants to Documentation
     • We want 2 variants for http://boost.filecoin.io/ – one for stable release, and one for unreleased / master version. Coordinate with Mayank and fix DNS / Gitbook for it.
5. • Changes to unrelease variant of Documentation
     • Tutorial for upgrading from Boost v1 to Boost v2
     • Explanation of boostd-data and how it interacts with YugabyteDB and LevelDB
     • Maybe add Deployment page that explains a full deployment and all processes of Boost (boostd, boostd-data, http, bitswap, lotus, lotus-miner, etc.) (currently this is Getting Started -> As a SP)
     • Add more docs on YugabyteDB – not a full copy-paste of YugabyteDB docs, but some explanation how to get started with it.
     • Downgrade Lotus -> Boost upgrade into a not-so-central page
     • Add documentation page on Storage- and Retrieval- in general why it is important for Retrieval- to be up and running (i.e. incentives, FIL+ data, Spade reputation, etc.)
     • Document that the connection to the LID service must be a websocket connection (not http)
     • Document what “unsealed”, “sealed”, “indexing” means

[LexLuthr]

Please add the following as well:

• Boost component overview - All binaries and what they do along with how they connect to each other
• How Boost talks to lotus - boundary between Boost, Miner and daemon
• All exposed ports and what they are used for - all security considerations
• Getting familiar with Boost UI - What each page contains and how to look up things
• How retrievals work - all 3 protocols showing where data comes from

[brendalee]

An additional item to consider (mostly for LID migration documentation) - after talking to Rob, could start compiling a list of FAQs on migration tooling.

For example:

• Do I need to run the migration in one go, or do I have an option to do it incrementally?
• Can I still make storage deals while doing the migration to LID?

[brendalee]

Please add the following as well:

• Boost component overview - All binaries and what they do along with how they connect to each other
• How Boost talks to lotus - boundary between Boost, Miner and daemon
• All exposed ports and what they are used for - all security considerations
• Getting familiar with Boost UI - What each page contains and how to look up things
• How retrievals work - all 3 protocols showing where data comes from

I'm going to separate out these documentation items as additional docs improvements, and not LID related documentation

[brendalee]

Issue created here: #1504