Broker for the Filecoin network
Join us on our public Slack channel for news, discussions, and status updates. Check out our blog for the latest posts and announcements.
This repository has been archived and is no longer maintained. If you are looking for an alternative tool to use, try one of these: Estuary, Web3 Storage, or lookout for the coming release of
Broker packs and auctions uploaded data to storage providers on the Filecoin network.
go get github.com/textileio/broker-core
Storage providers on the Filecoin Network can bid in storage deal auctions.
Refer to the Bidbot repo.
The bench.sh
script depends on the $SEED_PHRASE
environment variable for locking NEAR funds (the seed phrase itself is available in 1Password in "NEAR Developers").
$ REPO_PATH=. make up
$ cmd/storaged/bench.sh 127.0.0.1:8888 100 200 10 0.1
The k8
folder contains manifests to deploy the Broker system to a Kubernetes cluster.
The system is automatically deployed with the following rules:
- There are three environments:
edge
,staging
, andproduction
(these correspond to k8 namespaces). - Any push on any branch will trigger a deploy to
edge
if the commit message contains the substring[shipit]
😎. - Any push to
main
(including pull request merges) will trigger a deploy tostaging
. - Releases trigger a deploy to
production
.
A bot named uploadbot
also is available to run in any environment. To run it, go to the k8
folder and run DEPLOYMENT=<production|staging|edge> make run-uploadbot
.
A Grafana dashboard are available to have observability in the system. To sign in, use your GH account that should be part of the Textile organization.
Pull requests and bug reports are very welcome ❤️
This repository falls under the Textile Code of Conduct.
Feel free to get in touch by:
- Opening an issue
- Joining the public Slack channel
- Sending an email to contact@textile.io
A changelog is published along with each release.