Weird. When I disabled that setting Immich started asking twice for deleting images. I turned it back on and it went back to normal.
Edit: I think I misunderstood your original question. Do you want Immich to not ask for confirmation at all when deleting things?
Oh, right, sorry. I didn’t want to delete the app and reinstall it to find out which permission it was, so I just guessed from its existing permissions.
On my device the relevant toggle is located in Apps > Special app access > Media management apps.
I believe you need to choose “Always allow all” option in “Photos and videos” permission.
I currently run it in Kubernetes but I just translated my existing Docker setup to it. I recommend setting up PostgreSQL and Redis if you can for the best performance, but SQLite and no-cache-approach is also fine for the beginning (you just run a single container).
That being said, I think Nextcloud is not very cloud-native. I set up Redis just so I can do rolling updates with zero downtime (filesystem locks are kept in Redis’ memory instead of the app’s own), but I still get some server errors for a brief moment during updates (for less than 10 seconds).
Who said that? I really like it.
This might not be what you are looking for but in such cases I just use GParted running on a Linux Mint bootable thumb drive.
Though I don’t know if a similarly capable CLI alternative exists for headless servers.
Forgive my ignorance as I am very new to networking. Does it not look like it is the other way around? Your certificate manager tries to connect to Let’s Encrypt and fails? Even with DNS challenges, your certificate manager has to tell Let’s Encrypt to check your DNS records somehow.
What did you not like about Headscale? I started using it recently and it seems fine so far. Works identically to Tailscale.
I have been using T14s Gen 6 (AMD) and it works perfectly
BLOB already includes “binary”. That’s what the first B is for.
Sorry, couldn’t stop myself.
I don’t know much about it but I am all for open-source hardware.
I don’t see how systemd is in wrong here. Curious, what would you change about it?
When I need to create scratch files I usually operate in /tmp. Almost all directories there that I saw were using randomized paths (e.g. UUIDs). I guess this is to prevent problems mentioned in the article. So, I believe this would be a vulnerability of snap, not systemd.
I use Fedora where /tmp is created as tmpfs, which lives in RAM and is cleared when the system is shut down. I wonder what’s the benefit of Ubuntu’s approach.
Do they imply Wayland forces apps to have CSDs? It is only GNOME that does it.
I run it in a rootless Podman container using Quadlets. Instead of opening the server’s ssh port, I only port-forward the container’s ssh port (e.g. 22 -> 2222). I have sign-ups enabled, since I want people to be able to contribute (or just create issues). But I have configured the server so that nobody can create a repository. They can still fork my repos and send a pull request.
I have yet to experiment with Actions. I assume the safest option would be to only enable it for my own commits, but I am not sure.
I don’t think that’s possible currently. It is probably worth discussing on GitHub.