1·
1 year agoI use Traefik. It’s “fine” but Dessalines hates it.
- 0 Posts
- 15 Comments
Joined 11 months ago
Cake day: January 2nd, 2024
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
3·1 year agoperl-rename and a good regex. I’m not joking!
You’re on the right track. I’m on mobile so will be brief, edit from a laptop in a while.
You can use subdomains, which is my preferred way if making services work with traefik, but you could also look for, say,
example.com/potatoto get to the potato service; this may work better with DDNS.Edit: each subdomain needs to be updated, you might be able to get away with making them all a CNAME that points at the DDNS.
You’re correct in your assessment that you only expose 80 and 443 for the Traefik container and access everything else through that. Also only use 80 to redirect to 443.
Don’t expose the NAS directly to the web, instrad look at port forwarding on your router, it should be able to forward requests received on only 80 and 443 to the NAS while still blocking everything else.
My only complaint about Synology stuff is that I couldn’t get Traefik in swarm mode going!
Any questions reach out.
Edit2: consider looking at a cheap VPS or a static IP to eliminate the requirement to expose your NAS directly to the web. Alternately run your internal DNS for stuff (including SSL certs from LetsEncrypt) and VPN in (I use Wireguard) when you want to access it.
Close enough to 0 downtime that it doesn’t matter.
- Deploy updated stack file to existing stack
- existing services are updated
- Traefik polls the docker socket and notices updated labels
- ???
- Profit!
Seriously, you shouldn’t need to put anything (outside of rules that you want to re-use [e.g. http->https middleware]) in the traefik dynamic configuration because each container/service in a docker stack will bring with it its own configuration. Your only ‘dead time’ is how long it takes Traefik to pick up the new dynamic configuration via either the
dockerorswarmproviders, which is configurable but I’ve never had to touch because, even on production systems, it’s been fine.
With labels you just update the service definition by redeploying the stack; the dynamic file provider adds nothing in most circumstances.
You certainly don’t need to take down your container except to change things that are part of the Traefik static configuration.
Ok, that is weird and I retract my criticism. Just because I don’t see it doesn’t mean something unusual isn’t happening there!
I was wrong on the internet; apparently with certain Lemmy apps this directs to a completely different website.
What crack are you smoking? It’s literally a post about “building lightweight hardened containers”?Edit: wtf is townscaping? Is that like manscaping for a whole town? Or is it just regular landscaping.
It’s one of those tools that’s in a weird niche. If you need to use it you probably shouldn’t be exposing services to the internet. If you’re trying to learn it’s not going to teach you much. If you don’t need it you won’t use it anyway.
Insecure mode is enabling the dashboard.
Edit: if you get stuck here’s a quick demo Lemmy config. I have a traefik 3.0 instance setup there as well.
The safest way is to make a backup and restore it to the new array.
Your way sounds pretty fun though. I’m sure the firmware will complain, but once you have a solid backup you can go nuts!
Also consider a solution such as Bachefs - RAID is cool and all, but this will get you most of the way there too. (Decide on the data safety for yourself but I’m running a 90tb pool with 24tb of metadata / cache on SSD)
The better solution is to build containers without all of that bloat in the first place. I did up a post on that subject a little while ago.
I tend to use btrfs on single disks for reasons of snapshots (that I never use…), subvolumes, CoW, etc.
For my multi-disk needs (and single-disk stuff when it gets mainlined), bcachefs is my file system of choice. I’m currently running a 90tb spinning rust + 24tb metadata and cache on ssds on my archive / nas box.
You’ll have to do some reading, but here’s some (almost) turnkey repos for all the pieces you need to host Lemmy (and other things) in docker.
I use Traefik instead of nginx to do load balancing / edge routing / reverse proxy / SSL termination (and automatic generation via LetsEncrypt - it’s proven to be bulletproof in a good few production setups.
I’ve got mine all over the place. Typically I contribute to the Gentoo Wiki, but I recently started using my Lemmy instance for that, because why not?
https://lemmy.srcfiles.zip/post/3841
In terms of self hosting though, WordPress isn’t a bad option, and it’s often used for this purpose “in the wild”.
You mentioned that you don’t like the styling of MediaWiki - it’s possible to skin MediaWiki; the wiki version of that Lemmy post is hosted on a MediaWiki instance that doesn’t look like Wikipedia!
Other things to consider:
- static site generators
- pandoc markdown / RST -> html workflows
I’m sorry, but no. PluralKit only really impacts a tiny minority of the userbase to begin with. It isn’t enough to cause people outside that group to choose the platform, nor is it enough for people outside of that minority to avoid moving to whatever the next big thing is.