The zero config, self-managed, bitcoin lightning marketplace.
Take back ownership of your market!
Requires Docker
$ export ENABLE_TOR=true # optional
$ export TOKEN="YOUR STRIKE API TOKEN"
$ docker-compose up
If you don't yet have a strike api token, you can still explore the platform; merely unset your $TOKEN variable before run:
$ unset TOKEN
$ docker-compose up
Now, when you press the "pay with lightning" button, we will respond with mock data (id is all 0s).
You should be able to access http://127.0.0.1:8080
The inventory.yaml file is the heart of your marketplace.
The structure of this file should be simple enough for any user to manage, check out YAML if you need more detail.
Our inventory file contains a key called images for each product:
inventory.yaml
- name: Pancakes
tags:
- Tasty
description: |
More like tasty cakes, like very very tasty!
...
price: 0.01
image: pancakes.jpeg
content: pancakes.jpeg
These images are hosted within the static/images/ folder; for example,
pancakes.jpeg can be found at static/images/pancakes.jpeg
Our inventory file also has a key called content for each product,
as expected, these live in content/ and are only accessible through a valid
receipt page.
A receipt page is only valid when the following are true:
- invoice's state is PAID
- invoice created less than 24 hours ago.
The banner can be changed by replacing static/images/banner.jpeg with your own.
The look and feel of your application lives within your templates, more
accurately, your templates/ folder. You have the ability to change any
aspect of your marketplace and the full power of the
Jinja2 template
renderer.
Without adding much complexity, or more compute resources in the form of database servers, I decided to go with simple comma-separated values file.
As invoices are created, and as invoice are paid your sales.csv will grow.