[-] Asparagus0098@sh.itjust.works 1 points 1 day ago* (last edited 1 day ago)

You could also use a tempmail for the email https://adguard.com/en/adguard-temp-mail/overview.html

BTW do u know what the difference between the two PDFs they offer is?

[-] Asparagus0098@sh.itjust.works 10 points 1 week ago

i call it "butter FS"

[-] Asparagus0098@sh.itjust.works 9 points 1 week ago

This looks like a pretty fun show. I'm adding it to my plan to watch list. Thanks.

[-] Asparagus0098@sh.itjust.works 3 points 2 weeks ago

Yeah quadlets are pretty cool. I have them organized into folders for each pod. podman auto-update is also another pretty nice feature. I don't use the systemd timer for auto-update. Instead I just do podman auto-update --dry-run to check for updates and update my quadlet files and configs if any changes are required then I run the updates with podman auto-update.

[-] Asparagus0098@sh.itjust.works 3 points 2 weeks ago* (last edited 2 weeks ago)

podman-generate-systemd is outdated. The currently supported way to run podman containers using systemd services would be Quadlet files.

https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html

Edit: I just saw that you use debian so idk if Quadlets are a thing with the podman version on debian.

[-] Asparagus0098@sh.itjust.works 1 points 2 weeks ago

Any reason why you use compose and not quadlets?

[-] Asparagus0098@sh.itjust.works 3 points 2 weeks ago* (last edited 2 weeks ago)

Do you mean networking between them? There's two ways of networking between containers. One of them is to create a custom network for a set of containers that you want to connect between each other. Then you can access other containers in that network using their name and port number like so

container_name:1234

Note: DNS is disabled in the default network by default so you can't access other containers by their name if using it. You need to create a new network for it to work.

Another way is to group them together with a pod. Then you can access other services in that same pod using localhost like so

localhost:1234

Personally in my current setup I'm using both pods and seperate networks for each of them. The reason is I use traefik and I don't want all of my containers in a single network along with traefik. So I just made a seperate network for each of my pods and give traefik access to that network. As an example here's my komga setup:

I have komga and komf running in a single pod with a network called komga assigned to the pod. So now I can communicate between komga and komf using localhost. I also added traefik to the komga network so that I can reverse proxy my komga instance.

[-] Asparagus0098@sh.itjust.works 6 points 2 weeks ago

NewPipe on my phone. I don't have PC I can use rn but when I used to have one I'd just use my browser (mainly Firefox) with ublock origin to watch YouTube (without signing in).

Asparagus0098

joined 1 month ago