Asparagus0098

joined 4 months ago

It is the default atime option used when mounting if I'm correct. If it's an ubuntu specific mount option it will be specified in /etc/fstab file.

[–] Asparagus0098@sh.itjust.works 4 points 1 day ago (2 children)

You can run this to check

findmnt --real
[–] Asparagus0098@sh.itjust.works 1 points 2 days ago* (last edited 2 days ago) (2 children)

Do you actually need to move the admin ui off of port 80/443 if you are just forwarding ports? I don't think you need to. That said I actually don't know much about port forwarding since I use Tailscale because of CGNAT.

My understanding of port forwarding is that you are forwarding connections to your WAN IP/port to a LAN IP/port. Since the router admin ui is available only on LAN by default, you don't need to change it's port from 80/443.

[–] Asparagus0098@sh.itjust.works 2 points 2 days ago* (last edited 2 days ago) (4 children)

You don't need 2 reverse proxies as others have said. What I did is just add a DNS rewrite entry in my adguardhome instance to point my domain.tld to the LAN IP of my reverse proxy.

[–] Asparagus0098@sh.itjust.works 6 points 3 days ago* (last edited 3 days ago) (1 children)

I use some generic names.

  • Phone: phone
  • Current Laptop: fedora
  • Old laptop: laptop
  • Router: openwrt

Yeah obsidian's pretty nice. I use the daily notes feature built into it for my journal.

collapsed inline media

[–] Asparagus0098@sh.itjust.works 3 points 6 days ago* (last edited 6 days ago) (1 children)

I ran a podman quadlet setup as a test some time ago. My setup was a little like this:

  • Create a pod if the app uses multiple containers
  • Create a seperate network for each app (an app is either a single container or multiple containers grouped in a pod)
  • Add the reverse proxy container to all networks
  • I don't expose any ports to the host unless necessary

If you create a new network in podman you can access other containers and pods in the same network with their name like so container_name:port or pod_name:port. This functionality is disabled in the default network by default. This works at least in the newer versions last I tried, so I have no idea about older podman versions.

For auto-updates just add this in your .container file under [Container] section:

[Container]
AutoUpdate=registry

Now there's two main ways you can choose to update:

  1. Enable podman-auto-update.timer to enable periodic updates similar to watchtower
  2. Run podman auto-update manually
# Check for updates
podman auto-update --dry-run

# Update containers
podman auto-update

If you run adguard home it's pretty easy. Just add a DNS rewrite to your local IP.

collapsed inline media

[–] Asparagus0098@sh.itjust.works 4 points 6 days ago* (last edited 6 days ago) (1 children)

~~How are you running nginx and immich exactly? With containers or on the host?~~

I don't know nixos that much but that looks like nixos configuration to me, so it's running on the host I assume?