Skip to content
Lightning Network Daemon Developer Site
CSS HTML Python Ruby Shell
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

Lightning Network Daemon Developer Site

Developer guides and resources for the Lightning Network Daemon


This repository contains functionality for programmatically pulling guides from the lnd repo, using a Python script and Jinja2 templates to output markdown files, which are the corresponding pages in the fully rendered Jekyll static site.

Pay special attention to these files:

  • templates/ The Jinja2 template fed into the Python script, holding the Jeykll header to be prepended to the guide content pulled from Github. The templates dir also holds the templates for special cases where for example a dev site-specific footer needs to be appended
  • Update local guides to the latest version available
  • The Python script that uses local guides and Jinja template to strip out redundant titles, add page headers/footers, and output Jekyll markdown
  • Build static site from Jekyll markdown and deploy to Google Cloud Platform

The rest of the files in this repo are the standard Jekyll site files.

Running the site locally

Install Jekyll:

$ gem install jekyll bundler

Run the site and watch for changes:

$ bundle exec jekyll serve

Regenerating documentation

# Install Jinja for python templating
pip install Jinja2

Get the latest

curl -o -s

Get the latest gRPC guides

curl -o -s
curl -o -s

Let's run the script to render the guides:


Now that you're all set up, you can just run ./ to automatically pull the latest markdown files and render the local Jekyll docs.


The Lightning API is deployed with Google Cloud Platform. Visit this blog post for more information.


  1. Install Google Cloud SDK and authenticate into it:
brew cask install google-cloud-sdk
gcloud auth login
  1. Build
bundle exec jekyll build
  1. Push to Google Cloud Bucket
# -m use faster multithreaded uploads
# -d delete remote files that aren't in the source
# -r recurse into source subdirectories
gsutil -m rsync -d -r ./_site gs://

In the future, you can just run ./ to deploy automatically.

You can’t perform that action at this time.