Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
T
team
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 128
    • Issues 128
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • The Tor Project
  • TPA
  • team
  • Issues
  • #33750

Closed
Open
Opened Mar 27, 2020 by Hiro@hiro🏄Owner

Hosting BTCPayserver

BTCPayserver suggests to deploy and use the docker configuration in production.

The docker configuration is available via docker-compose: https://github.com/btcpayserver/btcpayserver-docker

BTCPay depends on several pieces of infrastructure, mainly:

A lightweight block explorer (NBXplorer),
A database (PostgreSQL or SQLite),
A full node (eg. Bitcoin Core)

There can be more dependencies if you support more than just standard Bitcoin transactions, including:

C-Lightning
LitecoinD and other coin daemons

It seems the bitcoin client needs to be installed and synced locally, therefore I am a bit concerned about storage. On this issue the docker setup has some scripts to prune the synced data to approx 100GB: https://github.com/btcpayserver/btcpayserver-docker#how-i-can-prune-my-nodes

I am also concerned how to make this setup play nicely with our infrastructure.

It would be nice if we can have an idea of the setup that BTC is currently running for us. What are the requirements? How many coins are supported?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: tpo/tpa/team#33750