LBRYCommunity/lbry.tech
1
0
Fork 0
Code Issues 13 Pull requests 8 Projects Releases Packages Wiki Activity

technically three sections

Browse source
This commit is contained in:
Jeremy Kauffman 2019-01-25 11:54:31 -05:00
parent 535d164628
commit 06344e4b71
1 changed files with 16 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

24
documents/build.md
View file

@ -11,30 +11,38 @@ Want to build something on top of LBRY? This is the place to get started.
At least, it's the place to get started so long as you have some idea of what LBRY _is_. If you don't, you should read the At least, it's the place to get started so long as you have some idea of what LBRY _is_. If you don't, you should read the
[Overview](/overview) first. [Overview](/overview) first.
Want to build with us rather than on your own? Check out our [Contributing Guide](/contribute).
### When to Use LBRY ### When to Use LBRY
- You want to build an application that contributes to the world's knowledge, or benefits from global, shared discovery (flesh this out). - You want to build an application that contributes to the world's knowledge, or benefits from global, shared discovery.
- You want to replace an existing centralized service related to digital content distribution with a decentralized/community-controlled one. - You want to replace an existing centralized service related to digital content distribution with a decentralized or community-controlled one.
- You want to build an application that is [[permissionless]] to interact with.
- You want to further openness, freedom of information, and/or personal choice on the internet.
### When Not to Use LBRY ### When Not to Use LBRY
- You want to privately distribute data/information. - You want to privately distribute data or information. LBRY is designed for publishing and sharing information in an open fashion.
- You want to do illegal things. - You want to do illegal things.
## Application Basics ## Application Basics
You can build many types of apps. You can build many types of apps. Fat apps, short apps, tall apps, skinny apps!
Most will use the [lbry-sdk](https://github.com/lbryio/lbry) as a way of accessing and communicating with the LBRY network. Most end-user applications will use the [lbry-sdk](https://github.com/lbryio/lbry) as a way of accessing and communicating with the LBRY network. A look at the [APIs](/api/sdk) provided by the SDK will help you understand what facilities the SDK provides.
Others might use lbrycrd, chainquery, lighthouse, torba, etc. Some applications do not need to access content available on the network (e.g. a wallet-only app, or a blockchain visualizer). These applications might use [lbrycrd](//github.com/lbryio/lbrycrd), the blockchain daemon, or [chainquery](//github.com/lbryio/lbrycrd), which parses blockchain data into SQL.
Let's look at some specific types of applications and the basic design for each.
### Web Applications ### Web Applications
#### Full Web Applications #### Full Web Applications
1. Set up a web server. By full web application, we mean a centrally-hosted web application that uses most or all of the suite of capabilities the LBRY protocol provides.
1. Install lbry. (Docker images? Other convenient ways of doing this?)
1. Pick your favorite language and stack and do your typical setup to get a "Hello World" application running.
1. Install [lbry-sdk](//github.com/lbryio/lbry). (Docker images? Other convenient ways of doing this?)
1. Bridging basics. 1. Bridging basics.
1. See SDK Basics 1. See SDK Basics