That’s it! If you don’t specify a host path, i.e. the path before the colon, Docker will create an volume which saves any changes you make to that path in the container, but won’t mount any existing path from the host to the container.
That’s it! If you don’t specify a host path, i.e. the path before the colon, Docker will create an volume which saves any changes you make to that path in the container, but won’t mount any existing path from the host to the container.
No users to answer questions? No problem…
Nice, looking forward to it!
Yes, I think that’s it. Their website really don’t make it easy to figure out…
/c/titlegore
You would need to set up routes on these other devices to tell them that VPN devices can be reached through the Pi. It’s possible, but I’ve never done it myself, so I don’t have any useful pointers.
Yes. All devices connected to the VPN will have a private IP inside the virtual network. You can use these to communicate as though they were public IPs, except that they can’t be used from outside the VPN.
There’s also a noticeable difference with some beans. Cheap ones are tough and taste almost stale, while nicer ones are creamier and more flavourful.
Yes, you can connect the device behind CGNAT to your existing VPN as a client. Then, from inside the VPN, you would use the its virtual address to connect to it. You can use a systemd service or similar to have the VPN connect at boot.
There are a few default instances in the settings page, and you can add your own as well.
There is also an other approach: encode your media a priori into a format that you can play direct, and then you don’t have to worry about transcoding performance. The advantage of this is that you can likely get better quality encodes.
deleted by creator
I can recommend Navidrome as a server. I’ve had great experience with it.
See this post: https://lemmy.world/post/77145
You remove the instance’s domain name from the URL, the same way you remove reddit.com
when linking to subreddits. You then append it at the end of the URL with an . For example,
https://lemmy.ml/c/asklemmy
--> /c/asklemmy .ml
EDIT: Starting with Lemmy 0.18.0, you won’t need to do this manually anymore!
Tailscale and Netmaker use wireguard under the hood, so as long as you manage to establish the connections, they should be just as fast! If you need to use relaying, however, that will introduce additional overhead.
I’ve tried from networks outside my home and I can access the server from there. Looking at a traceroute, I stop getting anything somewhere between my ISP and the datacenter the server is in.
I’m also not a fan of Wallabag, but Omnivore look excellent! Thanks for the suggestion!
I do this, too. I haven’t tried Tailscale, but Netmaker wasn’t able to deal with my CGNAT without a relay node, and I found that to be hit-and-miss.
Personally, I think Ubuntu is the most friendly distribution when you’re starting out, just because there are many tutorials written for it. I also think more things work out-of-the-box than on RedHat-based distributions.
He claimed he DMed the admins. I can’t see any public post about it.