~cypher/funding

Funding software development since the great collapse
Migrate Taler code to own package
Correct Bitcoin naming
Move service code to own package

refs

master
browse  log 

clone

read-only
https://git.sr.ht/~cypher/funding
read/write
git@git.sr.ht:~cypher/funding

You can also use your local clone with git send-email.

#Funding

Support your free and open source project with a form of crowd matching and giving users options for what to fund.

WARNING: Project is still in alpha, backwards incompatible changes will be made. USE AT YOUR OWN RISK.

#Building

Requirements:

go build ./cmd/funding

#Running

These are instructions to setup a playground. The project is unsuitable for production use.

Requirements:

#Quick Setup

You may want to create a directory from which to run the service. I chose to use a directoy under /srv.

mkdir /srv/funding

Move application and sample project into the folder.

# copy application to folder
cp funding /srv/funding

# copy sample configuration file and folder
cp -r testdata/config.yaml /srv/funding/funding.yaml
cp -r testdata/project_root/var /srv/funding

Start the service using your configuration file of choice. The service should still be customized to use your bitcoin service of choice.

cd /srv/funding
./funding -config funding.yaml

The project will now be accessible under http://[hostname]:[port]/project/Funding

#Webpage UI playground

You can customize the HTML UI without recompiling the project by placing the templates in a special folder.

cp -r asset/template /srv/funding/var

The service will have to be restarted for these changes to take affect. The entr command can be used to streamline this.

find var/template | entr -cr ./funding -config funding.yaml