History

Victor Shyba 7f4e813277 document schema update process		2021-06-02 12:05:36 -04:00
..
types	added support protobuf	2020-06-05 15:50:00 -04:00
__init__.py	moved lbry up one level	2020-01-01 15:57:56 -05:00
attrs.py	moved lbry up one level	2020-01-01 15:57:56 -05:00
base.py	moved lbry up one level	2020-01-01 15:57:56 -05:00
claim.py	fix update	2021-03-14 10:11:42 -04:00
compat.py	moved lbry up one level	2020-01-01 15:57:56 -05:00
Makefile	using multiprocessing.Manager to keep blocked content synced between readers	2020-01-20 12:49:41 -05:00
mime_types.py	Fix / Add correct mimetypes for HLS / DASH	2021-01-25 15:55:56 -05:00
purchase.py	moved lbry up one level	2020-01-01 15:57:56 -05:00
README.md	document schema update process	2021-06-02 12:05:36 -04:00
result.py	fixes from review	2021-03-24 16:30:33 -03:00
support.py	added support for signed supports	2020-06-05 15:49:18 -04:00
tags.py	moved lbry up one level	2020-01-01 15:57:56 -05:00
url.py	make better resolve cache	2021-03-19 19:58:13 -03:00

README.md

Schema

Those files are generated from the types repo. If you are modifying/adding a new type, make sure it is cloned in the same root folder as the SDK repo, like:

repos/
    - lbry-sdk/
    - types/

Then, download protoc 3.2.0, add it to your PATH. On linux it is:

cd ~/.local/bin
wget https://github.com/protocolbuffers/protobuf/releases/download/v3.2.0/protoc-3.2.0-linux-x86_64.zip
unzip protoc-3.2.0-linux-x86_64.zip bin/protoc -d..

Finally, make should update everything in place.

Why protoc 3.2.0?

Different/newer versions will generate larger diffs and we need to make sure they are good. In theory, we can just update to latest and it will all work, but it is a good practice to check blockchain data and retro compatibility before bumping versions (if you do, please update this section!).