Plugins, Not Forks
summary
BTCPay Server moves feature work out of core into an extensible plugin system: about 30 plugins live in a directory, plugins build from a plugin template (C# today, hoping for multi‑lang later), run locally by forking BTCP repo, adding the plugin solution, then launching the stack with docker compose up. Builds are automated from GitHub repos and versioned; marketplace does light verification only, plugins remain opt‑in so merchants avoid added points of failure.
AI-written summary · about
chapters (11)
- 0:00Plugins in BTCPay Server
- 3:53BTCPay's plugin architecture
- 7:29Current plugin ecosystem
- 12:13Customization via plugins
- 15:53Plugin types and use cases
- 21:27Plugin dev environment
- 27:12Local plugin connection
- 33:52Docker plugin testing
- 37:09Publishing to marketplace
- 42:30Live plugin demo
- 45:01Q&A on plugins
related talks
52mBTCPay Server Workshop
42mOpen Source Technology
16mPlugins: An internals deep dive
24mSpinnaker Extensibility: A Journey
30mWise approach for community & commercial Strapi plugins development
37mCoreDNS Deep Dive
32mAccelerating Collaborative Plugin Development
45mPlugin Oriented Programming A New Way to Scale Development
