I’ve used an old, out-of-support phone as a permanently plugged-in homeassistant control panel. Not quite self-hosting as in phone-server, but a fun easy project and a great way to keep an old device in use.
- 0 Posts
- 5 Comments
Joined 2 years ago
Cake day: July 31st, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
mlfh@lemmy.sdf.orgto
Selfhosted@lemmy.world•How do I stop Docker trying to pull from IPv6?English
3·4 months agoCan you give us the full output of the following commands?
ip addrsysctl net.ipv6.conf.all.disable_ipv6
mlfh@lemmy.sdf.orgto
Green Energy@slrpnk.net•Finland warms up the world’s largest sand battery, and the economics look appealing
9·6 months ago100MWh from that one little silo, that’s incredible.
mlfh@lemmy.sdf.orgto
Self-hosting@slrpnk.net•Building Cheap & Efficient Home Servers with... Laptops? | Hardware Haven
17·8 months agoIn my experience, mounting some thinkpad servers to the wall above the rack gives the homelab a very International Space Station feel.
The rclone fuse mount is essentially running in the memory of the container, and doesn’t translate back into the filesystem that the host presents from itself into that container.
Since rclone is available in the debian repos, the simplest and easiest option would be to do the rclone mount on the host and then pass that via bind mounting into the Plex container.
If you want to keep the rclone mounting containerized though (or if your Proxmox host is clustered, you want to mount it on the host, and you want the mount to be shared between your nodes), you can use rclone’s experimental but built-in nfs server feature: https://rclone.org/commands/rclone_serve_nfs/
Make sure your 2 containers can talk to each other over a secure network (“this server does not implement any authentication so any client will be able to access the data”), start the nfs server in the rclone container, and mount it via nfs in the Plex container.
Good luck!