Docker - connect to local Bitcoin Core node by default using env variables

[nmfretz]

I'm hoping to set up Specter Desktop via a docker-compose.yml with a default connection to a local Bitcoin Core node so that when a user boots up the app for the first time they are already connected to their Bitcoin Core instance. From their, the user could then decide to change to an electrum server or alternate Bitcoin node.

For context, this is for running Specter Desktop on Umbrel.

Currently, specter is running on Umbrel with version 1.14.2. With this version we were able to set up the Bitcoin node connection using environment variables, as seen here: https://github.com/getumbrel/umbrel-apps/blob/master/specter-desktop/docker-compose.yml

However, with newer versions of specter, the initial onboarding setup has changed with the introduction of the option to connect to Bitcoin Core or a public Electrum Server, and I can no longer set up a Bitcoin node connection using the same environment variables as before. I have an open PR here to update to Specter Desktop 2.0.1: https://github.com/getumbrel/umbrel-apps/pull/523

Has this functionality been removed, or are there other environment variables I can pass in to do this?

[smolgrrr]

Bumping this

[nmfretz]

We have updated to v2.0.2 in the Umbrel app store: https://github.com/getumbrel/umbrel-apps/pull/894. New installs on Umbrel will need to manually connect their umbrel bitcoin core node to Specter Desktop through the apps UI.

We would love to re-implement automatic bitcoin core connection upon install in the future!

[k9ert]

Sorry for the late reply. As specter is, in theory, a multi-node application, this could be due to all nodes having "autodetect": false,. So the question is why and how did they get to false?