2026-10-21 10:28 UTC
Replies (5)
-
@electric_nan@lemmy.ml 2026-10-21 14:35
Just want to give an alternative to Docker here: Yunohost. It’s very easy to setup and use, and while it doesn’t have the infinite number of “apps” that Docker makes available, it has served me very well. The project is also based in Europe :)
-
@hperrin@lemmy.ca 2026-10-21 11:41
It sounds like you just wants Nextcloud and maybe Immich. So here’s my suggestion: If you don’t have a domain yet, buy a domain. Preferably through Cloudflare because their API is good, and you’ll need that. Point an apex A record at your public IP address. Set up something like Kubuntu on the box itself. Make sure it has a static IP address (you can also do DHCP reserved through your router, which is safer), and forward ports 80 (TCP), 443 (TCP), and 51820 (UDP) to that box. Now comes the magic. Install docker through the official installation docs for Ubuntu (don’t use Ubuntu’s packages). Create a folder in your home directory called “services”. Inside this folder, you’re going to set up a folder for each service you need. The first one you should set up is “nginx-proxy-manager”. Inside each folder you’ll have a “docker-compose.yml” file. Inside that file, set up your docker compose stack. Nginx Proxy Manager’s is pretty simple. Just one service. But change the network mode to “host” (network_mode: host), and remove the ports section. nginxproxymanager.com/setup/ Now, from a terminal, in that folder, run docker compose up -d. Get used to that command, you’ll run it a lot. Then go to localhost:81, and create an account for NPM. Use a real email address, because that’ll be your contact email for Let’s Encrypt ssl. Go into the ssl settings and create a certificate. You’ll need an api key from Cloudflare, or whatever other place you bought your domain from. It needs access to change the dns settings for your domain. Use this format to create your certificate: example.com, *.example.com And use the dns challenge option where you’ll put your api key. [continuing in next post] Important Edit: One thing I forgot to mention, don’t use Docker volumes. Use a bind mount to mount a real directory inside the folder. It should look something like this: volumes: ./data:/data NOT like this: volumes: data:/data That way, when you back up that folder, it backs up all your data with it. If you use a docker volume (the one without the “./“), you’ll need to back those up separately. This is important for all of the mounts on every one of your services, especially the database services.
-
@Cyber@feddit.uk 2026-10-22 06:40
I suggest you have 2 separate physical devices. 1 - a NAS 2 - a server that you’re running everything on. Use OMV for the NAS if you’re not technical enough / want less maintenance and just keep your data there with only a backup app installed, On the other device pick whatever you’re comfortable with, docker is the mainstream choice, you’ll get loads of youtube / forum / lemmy support, but there’s other options of course. The advantage to this setup is that you can backup your server and if when you f*ck up you can restore it again. Less eggs in more baskets And as others have said, look at your router & internet security too
-
@lowspechq@lemmy.world 2026-10-22 07:06
cover. I wouldn’t pick TrueNAS unless you specifically want ZFS and its app model. Prebuilt: the DXP4800 Plus hardware is fine, but losing fan control, power management and hardware monitoring is exactly what people report losing when they replace a vendor OS — those bits usually live in the vendor’s own kernel modules or daemons. I haven’t run either of those two models, so I won’t vouch for them. Before buying, search “ + ” and look for a report from someone who actually did it; if you find nothing, assume it hasn’t been done. Backups: 3-2-1 — a local USB drive plus one copy offsite. A Hetzner Storage Box (1 TB is around €4/month) with restic or borg gives you encrypted offsite copies over SFTP, and both handle dedupe and retention. Whatever you pick: test a restore before you trust it. An untested backup isn’t a backup. Remote access: WireGuard on the FRITZ!Box is the right call and it sidesteps the dynamic IPv4 problem entirely — the box becomes the always-on endpoint. Just make sure you’re not exposing Nextcloud or Immich directly to the internet. Disclosure: I write a small site where I record measured numbers for running these services on low-spec boxes. The one on how far 4 GB actually gets you is here: lowspechq.com/best/best-self-hosted-ai-4gb-nas/ — if you’d rather not have a link in the answer, delete this last paragraph; everything above stands on its own.
-
@Decronym@lemmy.decronym.xyz 2026-10-22 07:10
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread: Fewer Letters More Letters CGNAT Carrier-Grade NAT DHCP Dynamic Host Configuration Protocol, automates assignment of IPs when connecting to a network DNS Domain Name Service/System IMAP Internet Message Access Protocol for email ISP Internet Service Provider NAS Network-Attached Storage NAT Network Address Translation NFS Network File System, a Unix-based file-sharing protocol known for performance and efficiency NUC Next Unit of Computing brand of Intel small computers RAID Redundant Array of Independent Disks for mass storage SATA Serial AT Attachment interface for mass storage SFTP Secure File Transfer Protocol for encrypted file transfer, over SSH SMTP Simple Mail Transfer Protocol SSD Solid State Drive mass storage SSH Secure Shell for remote terminal access UDP User Datagram Protocol, for real-time communications VPN Virtual Private Network ZFS Solaris/Linux filesystem focusing on data integrity nginx Popular HTTP server [Thread #144 for this comm, first seen 22nd Oct 2026, 07:10] [FAQ] [Full list] [@Two9A@hachyderm.io] [Source code]