Peertube?
Decentralised. Federated. activity pub. Self Hosted. Open source.
Lachlan, creator of lemmyunchained.net
Peertube?
Decentralised. Federated. activity pub. Self Hosted. Open source.
You seem on top of everything. No red flags when I look at what you are considering. Any will do great.
The Topnton i3-n305 Mini PC is a good choice. Intel NUC is another solid option, especially when used with a RAID enclosure for storage. Remember cooling is crucial for these devices, particularly if they’ll be housed in a small space. The importance of a good cooling solution cannot be overemphasized.
As for the operating system, Ubuntu is user-friendly and well-supported. You can run your desired applications like Plex or Jellyfin for media serving, qBittorrent, Sonarr, Radarr for torrenting, Wireguard for VPN, AdGuard or PiHole for ad-blocking, and Home Assistant for home automation, all on Linux. For managing these services, consider using Docker. It can help keep your system organized and simplify the process of updating. If you’re currently using them in a nas, you’re probably doing so already. But take the opportunity to clean things up, and if you’re not doing so already, use docker compose.
Foe backups, rsync can be used for local backups and Rclone for backing up to the cloud.
Yes. Because there’s no centralised list of communities, searching is extremely difficult. Or if not, very time consuming. Following every iteration of every node.
I’m not sure how that can be overcome.
I’m hosting one right now. Lemmyunchained.net
But in will have to Limit Users at some point.
I dont Think people properly understand they can be on any server. And join multiple communities. And it all Show up in their Feed. They don’t Need to worry about “which community has the Most Users”
AI GENERATED:
The ttionya/vaultwarden-backup tool is intended to work with Docker volumes. However, you are using a bind mount, not a named volume. Bind mounts refer to the use of local folders to store data, as in your case (./vaultwarden:/data/), while volumes create a specific place within Docker’s own filesystem for the data.
Although this tool is designed for volumes, it might still work with bind mounts if the backup container can access the data directory. You would need to modify the volume line in the Docker Compose file for the backup tool to point to the directory where your bind mount is located, i.e., to point it to your local ./vaultwarden directory.
So, you might want to adjust your docker-compose.yml file like this:
services: vaultwarden-backup: image: ttionya/vaultwarden-backup:latest container_name: vaultwarden-backup environment: - PUID=1000 - PGID=1000 - BACKUP_INTERVAL=12h - PRUNE_BACKUPS=7D volumes: - ./vaultwarden:/vaultwarden:ro - ./backups:/backups restart: unless-stopped
In this configuration, ./vaultwarden:/vaultwarden:ro line is the key. It mounts your local ./vaultwarden directory to /vaultwarden inside the backup container (readonly mode), which should allow the backup tool to access the data.