BTCpayserver

[timconsidine]

@nostrdev yes there is a public docker image
tcmbp132021/cloudron-customapp-installer:vX.Y.Z

I’m away at present so please check hub.docker.com for the correct version number.

Totally understand about credentials sensitivity.
You can check the code in the repo to see nothing is stored. And no metrics captured.
But feel free to manually use cloudron install —image tcmbp132021/cloudron-customapp-installer:vX.Y.Z after cloning the repo to have access to CloudronManifest.json

The hosted installer is purely a service, direct install is available.

I guess you could set up a special purpose Cloudron user and disable or change password after using it.

[timconsidine]

@nostrdev please upvote https://forum.cloudron.io/topic/14231/ccai-cloudron-custom-app-installer

[nostrdev]

done! we would like to add that the packaging team should prioritise the custom app installer over btcpay server (as we can easily deploy apps using the package installer from that point onward)

[LoudLemur]

What is the latest news on official support for BTCpayserver on Cloudron?

[timconsidine]

@nostrdev I'm trying to install btcpayserver after installing btc-core (and node fully synced)

I change the rpc auth in btcpayserver config.yml to match what is in btc-core bitcoin.conf

I restarted btcpayserver

I get a blank page on btcpay.domain.tl in Safari and a 500 error in Firefox.

btcpayserver logs :
Jan 07 16:57:24 fail: Microsoft.AspNetCore.Server.Kestrel: Connection id "0HNIE1J43J819", Request id "0HNIE1J43J819:00000001": An unhandled exception was thrown by the application.

I tried to set sysctl values but they're in RO location so will need a rebuild if wrong

Am I doing something wrong ?

Using https://git.nostrdev.com/stuff/cloudron-btcpay

[robi]

@timconsidine awesome, how much space does btc-core take up fully synced?

[nostrdev]

@timconsidine when you say the config matches, you mean this part right?

# Bitcoin RPC Configuration
bitcoin:
  rpc_user: "bitcoin"
  rpc_password: "xxxxx"

Note that the rpc_password should be the actual password, NOT the rpcauth= value in the bitcoin.conf file (which is derived from the password)

[nostrdev]

@robi for info, this is a non-pruned (full) node, as of today:

root@d1f00579-9662-4a14-896e-cf7cd8127709:/media/core# ls
banlist.json  bitcoind.pid  blocks  chainstate  debug.log  fee_estimates.dat  peers.dat  settings.json
root@d1f00579-9662-4a14-896e-cf7cd8127709:/media/core# du -sh
766G    .
root@d1f00579-9662-4a14-896e-cf7cd8127709:/media/core# 

[robi]

@nostrdev thanks, good to know.

You know the next question..

Pruned?

And is it sync-able already pruned?

[timconsidine]

@robi I pruned mine to 3Gb
I think somewhere I read pruning down to 600Mb might be possible. Maybe not lower.

[timconsidine]

@nostrdev thank you

Yes, I used the password value printed below that line as a comment.

I will dig bit deeper later