📄️ Quick Start
Bacalhau is a peer-to-peer network of computing providers that will run jobs submitted by users. A Compute Provider (CP) is anyone who is running a Bacalhau compute node participating in the Bacalhau compute network, regardless of whether they are hosting any Filecoin data.
📄️ Quick Start Using Docker
Good news everyone! You can now run your Bacalhau-IPFS stack in Docker.
Bacalhau uses libp2p under the hood to communicate with other nodes on the network.
📄️ Storage Providers
Bacalhau has two ways to make use of external storage providers:
📄️ Job Selection Policy
When running a node, you can choose which jobs you want to run. This is done by passing a combination of --job-selection type flags to bacalhau serve.
📄️ Resource Limits
These are the flags that control the capacity of the Bacalhau node, and the limits for jobs that might be run.
📄️ Test Network Locally
Before you join the main Bacalhau network, you can test locally.
📄️ GPU Support
How to enable GPU support on your Bacalhau node.
📄️ Configuring node persistence
How to configure compute/requester persistence
📄️ Windows Support
Running a Windows-based node is not officially supported, so your mileage may vary. Some features (like resource limits) are not present in Windows-based nodes.
Bacalhau supports the three main 'pillars' of observability - logging, metrics, and tracing. Bacalhau uses the OpenTelemetry Go SDK for metrics and tracing, which can be configured using the standard environment variables. Exporting metrics and traces can be as simple as setting the OTELEXPORTEROTLPPROTOCOL and OTELEXPORTEROTLPENDPOINT environment variables. Custom code is used for logging as the OpenTelemetry Go SDK currently doesn't support logging.