deleted by creator

deleted by creator

Bonus when you disable software flow control: In addition to Ctrl+r to reverse search through commands, you can search forward via Ctrl+s

deleted by creator

Using podman-compose, I usually have a section like:

volumes:
    - ./local_folder:/container/folder

Specifically, I have to use either an absolute path or a relative path with “./” to prevent it from treating a directory as a volume name.

Yeah, I’m confused by this video (which is from nearly a year ago, btw). It looks like a gnome shell overview more than anything.

My practical answer: Nah, it’s probably not going to nuke your files.

My software engineer answer: Never trust us to not make a mistake. It doesn’t take much to accidentally nuke a directory.

Agreed, for me containers are really nice for playing with new software without dirtying my host install.

Well good thing I finally realized it wasn’t enabled and set my environment variables to enable it.

Based, mostly

And even then, a properly configured SSHD instance wouldn’t really benefit from a firewall, unless you wanted to block all countries besides your own or something.

Every computer has a bunch of ports (1-65535 if I recall correctly), each of which is a unique entity to which a single service can bind. In layman’s terms, a port is a door that one service is able to answer when someone knocks. By convention, some ports have a specific associated service (80 = HTTP, 443 = HTTPS, 22 = SSH), but there are a lot that you can just use as you deem appropriate.

If you want a service (e.g. a web server) to be accessible, you have to run a service that binds to a known port (e.g. 80), and a client has to reach out to your server on that same port. A firewall sits between your service(s) and any potential clients, much like those steel security screen doors. If that’s closed, nobody gets through on that port, even if a service is bound to that port and is listening for a connection.

As a general rule of thumb, you want your firewall to block as much traffic as possible without breaking something (I.e. blocking one of your public-facing services). If you don’t run any services on your computer (web services, media servers, etc.), you can probably get away with blocking all inbound traffic. without any discernable impact.

Khal looks promising:

https://github.com/pimutils/khal

I’m actually almost completely unfamiliar with Nginx, short of a few hours of tinkering. NginxProxyManager is a direct competitor to Caddy, with a graphical interface, SSL cert creation and auto-renew, etc. I’m not going to say to switch from Caddy, since there’s probably no major benefit, but it’s much nicer than trying to figure out Nginx reverse proxies by hand.

I think the problem is that normal consumers wouldn’t ever buy a tape drive, so the only options still being produced are enterprise grade. The tapes are still pretty cheap, but the drives are absurd.

I really want to use tape for backups, but holy expensive. Those tape drives are thousands of dollars.

I’m going to cast another vote for a reverse proxy, such as NginxProxyManager. It’s really easy to set everything up, and they’re usually very easy to run in Docker/Podman.

One thing to note: if you end up with a domain with mandatory HSTS, you’ll have to use DNS-based certificate generation rather than HTTP based, since unencrypted HTTP is blocked (chicken/egg problem to get HTTPS working). It’s not hard, but you have to be aware of that limitation.

Ah, I’ve almost always used a single monitor setup, so my use case wasn’t weird enough to break X11. That said. Even Wayland is wonky on my multi monitor setup at work, though that’s probably more a GNOME thing than a Wayland thing.

I do still think the approach they took with Wayland is a tad odd, in that everyone has to implement it themselves. But hey, if it works, it works.

old

Old doesn’t mean bad

broken

Is it?

unmaintained

Is it?

I use Wayland personally, but I’ve had almost zero issues with X in the last decade, maybe with the exception of minor screen tearing several years back.

Or create a service running with limited access to specific resources, and create an API for users to make requests to that service.