Yeah, for learning you could run the node on your daily driver. But for production I would not do that, I think it needs to be a dedicated machine.
Discussion
That much makes sense - this is all education mode at the moment
VPN question… if the computer with the node uses a vpn service that periodically connects to different servers around the world, presumably that changes the device’s publicly-available IP address. Wouldn’t that make it very difficult to reliably connect to it from a remote wallet? Or is there a way of getting around that if you know the device already?
Yes, it 100% make more difficult because that particular computer’s external IP would be constantly changing.
Implicit in a question I asked yesterday about your setup, I gave you my (partial) solution to that problem.
Let’s say that computer stays at home and it connects to the external world through a VPN. That computer still lives within your home intranet, which means I can have a static intranet IP assigned to it.
So what I was thinking is that you would first need to make a connection to your intranet from the outside and then you connect to the node using its static intranet IP.
There’s still missing pieces to complete that puzzle, as you need to overcome the fact that your router’s external IP is most likely not static, but it’s a start.
Thanks for all the insight, Paulo 🙏⚡️
I had a feeling it might be trickier than expected haha. I think starting with the single device is the move, to learn the ropes here.
Was watching a nostr:npub1rxysxnjkhrmqd3ey73dp9n5y5yvyzcs64acc9g0k2epcpwwyya4spvhnp8 vid on connecting to MyNode; once I’m comfortable with the laptop+core setup, the node-in-a-box game (or perhaps StartOS on the old laptop) is next on the list.
Wonder if that’s easier to access remotely, since it’s tailor-made for these things.
I’ll be back with questions 🫡
🫡