LogoLogo
v1.x (Deprecated)
v1.x (Deprecated)
  • What is Boost?
  • Features
  • Architecture
    • Repository
    • Database
    • DAG store
    • libp2p Protocols
  • Hardware requirements
  • Getting started
    • As a storage provider
    • As a client
  • Migrate from Lotus to Boost
    • Migrate a monolith lotus-miner to Boost
    • Migrate a Lotus markets service process to Boost
    • Roll back to Lotus markets service process
  • Configuration
    • UI Settings
    • HTTP Transfer limit
    • Deal Filters
    • Remote CommP
    • Legacy Deal configuration
    • HTTP indexer announcement
  • Backup and Restore
  • Tutorials
    • How to store files with Boost on Filecoin
    • Using filters for storage and retrieval deals
    • Setting up a monitoring stack for Boost
  • Bitswap Retrieval
  • HTTP Retrieval
    • Serving files with booster-http
  • Troubleshooting
  • Experimental Features
    • FVM Contract Deals
    • Local Index Directory
      • Architecture
      • Requirements
      • Initialisation
  • GraphQL API
  • JSON-RPC API
  • FAQ
  • Need help?
Powered by GitBook
On this page
Edit on GitHub
Export as PDF
  1. Architecture

Repository

By default the Boost daemon repository is located at ~/.boost

It contains the following files:

  • api The local multi-address of Boost's libp2p API

  • boost.db The sqlite database with all deal metadata

  • boost.logs.db The sqlite database with the logs for deals

  • config.toml The config file with all Boost's settings

  • repo.lock A lock file created when Boost is running

  • storage.json Deprecated (needed by legacy markets)

  • token The token used when calling Boost's JSON RPC endpoints

It has the following directories:

  • dagstore Contains indexes of CAR files stored with Boost

  • datastore Contains metadata about deals for legacy markets

  • deal-staging The directory used by legacy markets for incoming data transfers

  • incoming The directory used by Boost for incoming data transfers

  • journal Contains journal events (used by legacy markets)

  • keystore Contains the secret keys used by libp2p (eg the peer ID)

  • kvlog Used by legacy markets datastore

PreviousArchitectureNextDatabase

Last updated 2 years ago