Geyser is a bitcoin & nostr native crowdfunding platform where you can fund project ideas with the support from global communities.
Launch your project »
Explore live projects
·
Report Bug
·
Request Feature
Table of Contents
Where great ideas find great communities
Traditional Crowdfunding and Creator Platforms are built on closed monetary and social networks, which limits the use of crowdfunding (a powerful financial primitive) to around 30 Western countries and restricts project reach and social interaction to the platform.
Geyser is enabling the Open Creator Economy, by building fundraising on top of open Bitcoin/Lightning, open monetary networks, and Nostr, an open social network. With these tools we can empower creators globally to reach their communities and raise funds from them.
As an open company, we also build Open Source software and rely on the support of contributors to change the world for the better.
This section should list any major frameworks/libraries used to bootstrap your project. Leave any add-ons/plugins for the acknowledgements section. Here are a few examples.
Yarn We use yarn as a dependency manager, install yarn if not already installed
npm install --global yarn
Docker ( optional )
We can use docker
and docker compose
for local development of the geyser-app
.
If you prefer using docker for development, make sure to have them installed on your local development machine, see here.
Clone the repo, get into the repo directory and run:
yarn
The app requires some environment variables to be set. We provide an example.env
file that you can copy to the a local .env
file:
cp .env.example .env
From there, populate the new file with the correct values. You have three development environment options, detailed below. It is recommended to use the staging API for most development tasks.
Optionally create .env.staging
file, that could be tried out for staging development
Make sure to complete the instructions described in Hosts Configuration, before proceeding using this method.
Currently, the staging API is the only way to get a functional authentication flow in standalone geyser-app
development environment.
To use the staging API, fill in the following value in the .env
file:
[OPTION A: STAGING]
REACT_APP_API_ENDPOINT=https://api.staging.geyser.fund
Start the server:
make dev-staging
If you do not require a functional authentication flow for this task, you may use this option.
[OPTION B: GRAPHQL_FAKER]
REACT_APP_API_ENDPOINT=https://api.dev.geyser.fund
APOLLO_KEY=<your Apollo Studio API key>
if you don't have an APOLLO_KEY
yet. Please Contact us
Start the server:
make dev-faker
Many at times we prefer using staging API while sometimes we prefer the local server. In such cases we can setup to use them interchangably.
- Create the normal
.env
file, which contains the values for local server. Refer to the.env.example
and useConfiguration 3-A
Start the server:
yarn dev
- Create a new file
.env.staging
this would have the values to use the staging API. Refer to the.env.example
and useConfiguration 3-B
.
Start the server:
yarn dev:stage
If you run into problems running the app through make command, you can run the app by running the following command in the project directory, as long as one of the docker configuration above ( Option 1 or 2) is satisfied.
docker compose up -d
Or, if you are running an older version of docker and have docker-compose installed separately, run:
docker-compose up -d
To see the react app logs use the following command:
docker compose logs -f geyser-app
or
docker-compose logs -f geyser-app
In order for the requests to go through to the staging backend API, you will need to add the following line to your /etc/hosts
file:
127.0.0.1 staging.geyser.fund
This makes sure that you are able to make requests to the staging API from your local development environment with encountering CORS errors.
If running against the GraphQL Faker server, you'll also need these in the same /etc/hosts
file:
127.0.0.1 dev.geyser.fund
127.0.0.1 api.dev.geyser.fund
We are using Caddy as a reverse proxy to serve the local development app over HTTPS. This means that you will need to trust the Caddy Local CA Certificate in order to avoid any ERR_CERT_AUTHORITY_INVALID
errors in your browser.
To do so, you can run the following command from the project root directory after starting the app and caddy server:
sudo yarn caddy:trust-ca
This command will add the Caddy Local CA Certificate to your system's list of trusted certificates (only works on MacOS for now). It needs sudo rights for that.
With Docker running, navigate to the URL that's appropriate for the development-environment configuration in your .env
file:
Make sure to also browse to https://api.dev.geyser.fund/ and accept the certificate there.
This will allow you to get around any
ERR_CERT_AUTHORITY_INVALID
errors that may be thrown in your browser.
See the docs on
GraphQL Faker Tips & Tricks
for more useful tidbits of information on running/developing the app against Faker.
See the open issues for a full list of proposed features (and known issues).
Contributions to Geyser are always welcome!
-
📥 Pull requests and 🌟 Stars are always welcome.
-
Read our contributing guide to get started,
-
Read our style guide to know more about style considerations.
-
Read our Architecture guide to learn more about the project.
or find us on Discord, we will take the time to guide you.
This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
- Stelios Rammos - @steliosats - [email protected]
- Sajal Dulal - @sajald77 - [email protected]
Use this space to list resources you find helpful and would like to give credit to. I've included a few of my favorites to kick things off!