BTCpayserver
-
We put an ad up on Satshoot and got a response today: https://satshoot.com/naddr1qvzqqqrllupzqf6g0jtqpvttyjsmlvz3nnly5hg6mpy4nc7vuhtd02vafpnq58mcqy88wumn8ghj7mn0wvhxcmmv9uq3wamnwvaz7tmjv4kxz7fwwpexjmtpdshxuet59uqsuamnwvaz7tmwdaejumr0dshsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshsz9mhwden5te0vf5hgcm0d9hx2u3wwdhkx6tpdshsq2zyv4cxcmme94p9gsed2pshjt2nv4e8vetj946x7t2rd3hh2erjdahz6vrsvvm8vecla3c7h/
Watch this space: https://git.nostrdev.com/stuff/btcpay-cloudron
-
This wasn't as straightforward as we hoped. Mainly because there are three components to this:
- Bitcoin core. For this we will just leave it as an external dependency.
- NBXplorer. This needs to be internal, but is a separate container.
- BTCPay Server.
The problem we're having is packaging two containers (NBXplorer + BTCPay Server) inside the same cloudron container. Does anyone have examples where this has been done on other apps?
-
This wasn't as straightforward as we hoped. Mainly because there are three components to this:
- Bitcoin core. For this we will just leave it as an external dependency.
- NBXplorer. This needs to be internal, but is a separate container.
- BTCPay Server.
The problem we're having is packaging two containers (NBXplorer + BTCPay Server) inside the same cloudron container. Does anyone have examples where this has been done on other apps?
@nostrdev said in BTCpayserver:
The problem we're having is packaging two containers (NBXplorer + BTCPay Server) inside the same cloudron container. Does anyone have examples where this has been done on other apps?
Without knowing specific technical details: You could install both applications (not as containers but as binaries/from source) into a single package, then use supervisor to start both of them.
There are a lot of examples on cloudron packages with multiple services in them, these two for example:
- https://git.cloudron.io/packages/librechat-app (Librechat & Meilisearch)
- https://git.cloudron.io/packages/gitlab-app (Gitaly, nginx, puma, sidekiq & sshd)
-
Thanks! We were able to resolve it in the end (was an issue with the nginx config). We now have btcpay server up and running, and plan to have the repo ready to publish here later this week
-
The server needs plugins to support additional currencies like e.g. Monero or Ethereum. I hope that the package will be able to manage these ok.
Other plugins would be helpful too, for example its ability to hook into woo-commerce and lightning
Especially, we hope Sideshift is easy to use
Fixedfloat and Sideshift are both instant cryptocurrency exchange services used as plugins in BTCPayServer, allowing merchants to accept altcoins by converting them to Bitcoin, with no clear winner based on features alone.
Sideshift seems to have more active development with modern technologies and GitHub activity, while Fixedfloat has a longer operational history since 2018.
Sideshift likely has a larger userbase, with over $2.0 billion in transaction volume, compared to Fixedfloat, where userbase size is less quantifiable.
Sideshift has open-source components (e.g., toolkit under MIT license), while Fixedfloat does not appear to be open-source. -
The server needs plugins to support additional currencies like e.g. Monero or Ethereum. I hope that the package will be able to manage these ok.
Other plugins would be helpful too, for example its ability to hook into woo-commerce and lightning
Especially, we hope Sideshift is easy to use
Fixedfloat and Sideshift are both instant cryptocurrency exchange services used as plugins in BTCPayServer, allowing merchants to accept altcoins by converting them to Bitcoin, with no clear winner based on features alone.
Sideshift seems to have more active development with modern technologies and GitHub activity, while Fixedfloat has a longer operational history since 2018.
Sideshift likely has a larger userbase, with over $2.0 billion in transaction volume, compared to Fixedfloat, where userbase size is less quantifiable.
Sideshift has open-source components (e.g., toolkit under MIT license), while Fixedfloat does not appear to be open-source. -
So it's looking like next week now, that btcpay server will be ready (as in, tidied up). The reason being, that we've also decided to package up Bitcoin Core, and that has a few idisyncracies (eg we need to document how to set up a cloudron volume, so that the blockchain doesn't get backed up)
If anyone is in urgent need of a btcpay server, knows how to deploy from cloudron CLI, and has their own BTC Core RPC creds - feel free to send a DM and we'll give you repo access
Otherwise, watch this space!
-
Finally - we have packaged Bitcoin Core!
How do we submit this for official packaging?
-
Finally - we have packaged Bitcoin Core!
How do we submit this for official packaging?
-
More good news - we also finally got btcpay server running: https://git.nostrdev.com/stuff/cloudron-btcpay/
Even better, it will automatically connect to your bitcoin instance. And you can have multiple BTCPay Server instances with just one instance of bitcoin core.
-
@nostrdev-com I would be happy to add another 100 euros (in btc) to the bounty. Over the long run it will be cheaper than the VPS Iām currently hosting my BTCPar Server on.
@jtippetts - we ended up doing this internally. If you're able to get value from this package, and still keen to contribute 100 EUR, we'd be super happy if it went to the Graphene OS project. We are not affiliated, we are just very grateful that their software exists.
-
Finally - we have packaged Bitcoin Core!
How do we submit this for official packaging?
@nostrdev said in BTCpayserver:
How do we submit this for official packaging?
Traditionally create a repo on git.cloudron.io but maybe the Cloudron team can work with your one.
Just mention @staff (ooo, I did) and they can take a look
-
@nostrdev said in BTCpayserver:
How do we submit this for official packaging?
Traditionally create a repo on git.cloudron.io but maybe the Cloudron team can work with your one.
Just mention @staff (ooo, I did) and they can take a look
-
@timconsidine - it seems there is no signup option
-
By default, GitLab allows external people to sign up. This can be disabled to restrict use only to Cloudron users as follows:
GitLab > Admin area > Settings > Features > remove the check mark "Sign-up enabled"
Maybe it can't detect your cloudron status
-
Hello @nostrdev and @timconsidine
Signup to the git.cloudron.io instance was disabled due to an overwhelming amount of spam accounts.
@nostrdev I will take this as a request for an account and access rights to create repositories.The @staff will create your account with the e-mail address used here in the forum.
