-
Notifications
You must be signed in to change notification settings - Fork 76
Closed
Description
-
- Document LID architecture- https://boost.filecoin.io/experimental-features/local-index-directory
-
- Document LID requirements - https://boost.filecoin.io/experimental-features/local-index-directory/requirements
-
- 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
- Document LID migration - https://boost.filecoin.io/experimental-features/local-index-directory/initialisation
-
- Add variants to Documentation
- We want 2 variants for http://boost.filecoin.io/ – one for
stablerelease, and one forunreleased / masterversion. Coordinate with Mayank and fix DNS / Gitbook for it.
- We want 2 variants for http://boost.filecoin.io/ – one for
- Add variants to Documentation
-
- Changes to
unreleasevariant of Documentation- Tutorial for upgrading from Boost v1 to Boost v2
- Explanation of
boostd-dataand how it interacts with YugabyteDB and LevelDB - Maybe add
Deploymentpage 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
- Changes to
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
Done