Skip to content

DirectSponsor/.github

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

1 Commit
 
 

Repository files navigation

Contributing

Thanks for your interest. This is a small open-source project run by one person. Contributions of any size are welcome — from fixing a typo to taking on ongoing maintenance.

What this project is

A set of websites and infrastructure that facilitate direct Bitcoin Lightning payments between sponsors and recipients in Ghana, Kenya, and elsewhere — no intermediaries, no platform fees. The main sites are:

  • directsponsor.net — peer-to-peer fundraising and sponsorship groups
  • clickforcharity.net — PTC (paid-to-click) site that earns sats for charity
  • roflfaucet.com — Bitcoin faucet

All are file-based, minimal-dependency, designed to work on slow connections and ageing hardware.

How the infrastructure is organised

  • Five VPS servers (es1, es3-auth, es5, es7, RN1) running Debian/Apache/PHP
  • Monitoring and alerting scripts in this repo (satoshihost/monitors)
  • Each site has its own repo with an AGENTS.md or README.md explaining its structure
  • Server-side cron scripts live on RN1 with local copies in monitors/server-scripts/rn1/

The monitors repo is the best place to start — it documents all running scripts, alert channels, and server layout in one place.

Reading the code

Each repo has an AGENTS.md (or PROGRESS.md) that explains:

  • What the project does
  • Its file/data architecture
  • Known gotchas and decisions made
  • What still needs building

Read that file first. It is kept up to date.

What kind of help is useful

  • Ongoing monitoring — checking Telegram alerts, investigating anything unusual
  • Small fixes — bugs, broken links, edge cases as they come up
  • Documentation — keeping AGENTS.md and PROGRESS.md accurate
  • New features — sponsorship group tooling, Nostr integration, LNURL-pay (all documented)
  • Security — reviewing cron scripts, PHP endpoints, auth flow

There is no roadmap with deadlines. Work at whatever pace suits you.

Getting started

  1. Read monitors/ALERTING-PLAN.md for a map of what's running and where
  2. Read directsponsor.net/AGENTS.md for the main site architecture
  3. Ask for SSH access to the servers if you want to dig deeper

Ground rules

  • Keep things simple — the philosophy is static-first, minimal dependencies, every byte justified
  • Don't introduce npm, databases, or heavy frameworks without discussing first
  • Prefer a one-line fix over a refactor
  • The people receiving payments are real — treat data carefully

Contact

Raise an issue in any repo, or reach out directly via the contact details on directsponsor.net.

About

Organisation-wide community health files

Contributing

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors