No description
Find a file
2021-09-26 21:26:39 +02:00
.github/workflows chore: exclude lnd grpc files from code scanning 2021-08-14 13:08:34 +02:00
.vscode feat: add a launch configuration for vscode 2021-07-25 17:25:32 +02:00
app fix: update wrong PyJWT version 2021-09-25 17:58:53 +02:00
.env_sample feat: implement get a raw system logs endpoint 2021-09-20 11:22:50 +02:00
.gitignore refactor: move some config vars to the .env file 2021-07-25 17:24:33 +02:00
__init__.py initial commit 2021-06-10 21:13:26 +02:00
LICENSE Create LICENSE 2021-09-23 21:03:34 +02:00
main.py fix: handling of multiple SSE clients 2021-09-26 21:26:39 +02:00
poetry.lock feat: redirect index route to latest api docs 2021-09-26 18:11:32 +02:00
pyproject.toml feat: redirect index route to latest api docs 2021-09-26 18:11:32 +02:00
README.md docs: update readme with poetry shell command 2021-09-20 19:44:11 +02:00
requirements.txt feat: redirect index route to latest api docs 2021-09-26 18:11:32 +02:00

blitz_api

Configuration

Create a .env file with your bitcoind and lnd configuration. See the .env_sample file for all configuration options.

Please note that you will also need to install Redis.

If you need a easy option to run a simple bitcoind & lnd client, Polar makes that pretty easy.

Installation

You will need to have Python in version 3.7 installed and have the .env see Configuration configured correctly first.

⚠️ To setup a development environment for BlitzAPI skip to the Development section.

To install the dependencies, run

python -m pip install -r requirements.txt on Linux / macOS or

py -m pip install -r requirements.txt on Windows.

After that, you can run the application with

python -m uvicorn main:app --reload on Linux / macOS or

py -m uvicorn main:app --reload on Windows.

Development

For development it is recommended to have python-poetry installed. Install instructions can be found here

From within the blitz_api folder open a shell via poetry shell.

Install dependencies with all dev dependencies: poetry install

If any dependencies have changed it becomes necessary to freeze all requirements to requirements.txt:

poetry export -f requirements.txt --output requirements.txt

This will skip all dev dependencies by default.
This step is required to avoid having to install poetry for final deployment.