Both CachyOS and ALHP are reasonably popular

never heard of them. I need to research a bit more until I activate what is basically another “dangerous” non-maintainer repository. Thank you a lot for your links and explanations!

How can I trust them? At least with Arch there’s the “many eyes” principle.

Can I also compile a list of selected packages from the repositories fresh easily? E.g. Firefox? Or do I have to download their PKGBUILD to makepkg?

You can reduce transmit power and enable meshing and roaming in conjunction.

Where’s the difference between march=native and march=x86-64 in that case?

why is that?

thanks for reminding me. Didn’t activate this on my new install since I got 64G of RAM :)

systemctl --user enable psd-resync.service

I think this is not needed since psd.service has the following in it:

[Unit]
…
Wants=psd-resync.service

What does that have to do with Linux?

You can test it on https://u2f.bin.coffee/

Here’s a Github issue about NFC on phones: https://github.com/solokeys/solo1/issues/209

Seems to not work for lots of people.

Sadly all of our huge customers use MS Office and we have to dogfeed ourselves with the whole MS 365 suite. That’s 70€ per month per user down the holes of Microsoft execs.

Why require keycloak specifically? Maybe I want to use another authentication gateway.

Macs had TPMs before Windows PCs, IIRC.

If you forget both, you upgraded the drive to a paperweight.

That’s why I have a password manager on my phone.

Ideas what you can do. These are all SHOULD and not MUST requirements, so pick and choose what you can reasonably do in a realistic timeframe without overburdening yourself. Some of these steps can be outsourced to your community.

You can try to make a twelve factor app but some of their advice is probably not suited for your application. You will end with some 7.5factor app which is fine.

Follow SemVer and provide detailed instructions for upgrading major versions.

Use a build system which is easily installable and a language where you don’t have to upgrade dependencies every second for security issues (looking at you, npm/nodejs).

Don’t include a webserver which does HTTPS, let the people run their own reverse proxy.

Test your setup with and provide multiple web server configs for nginx, Apache2, Caddy, Traefik.

Test your setup with and provide multiple default configs for bare metal (with a dependency manager), Docker, Podman, Kubernetes, Kata Containers.

If you need a DB, include the possibility to migrate from a self contained one instance SQLite to a multi container pgsql/MySQL setup.

Write database migrations in both directions so people can downgrade on failures.

Make it possible to configure your system via ENV variables, ENV files and config files. Provide instructions on best practices and sane defaults. Explain these defaults and make clear configuration is optional.

Make it possible to disable authentication to add Authelia or LDAP through the webserver. Make clear that this is only to be used for external authentication.

Make it possible to run multiple parallel instances of your software without affecting the database consistency, e.g. for high availability or horizontal scaling.

Provide a versioned, documented API (does not need to be public) and use it yourself for your frontend. Provide a telemetry endpoint which is human readable and machine readable, so Prometheus or a similar system can scrape it.

Basically, stock markets are based on predictions. If it is likely a stock will continue to fall, it is called a drop. You can not know if it’s a dip or a drop in advance because rising and falling stocks are always relative to the rest of the environment. So calling it a drop would be not wrong, but an unlikely prediction.

it’s podman-compose instead of podman compose

Don’t use it, it’s not a full replacement. The script is barely maintained and not really “official”.

I think before switching from Docker to Podman you should first get proficient in Docker, because Podman is not for beginners (yet).

Generally, “dip” carries the connotation that there will be a rebound, or a return to the original position. A “drop” however would mean that this would hurt the company in the long run.

It’s a dip, not a drop. Maybe you want to mitigate the sensationalist headline.

Installing Docker on a QNAP device is straightforward, thanks to the integrated Container Station application. Here’s how you can do it:

1. Install Container Station: Log in to your QNAP device’s web interface (QTS), and open the App Center. Search for “Container Station” and install it.

2. Enable SSH: If you need SSH access, go to the Control Panel > Telnet / SSH, and enable the “Allow SSH connection” option. Click “Apply” to save the changes.

3. Create a Docker Container: Once Container Station is installed, you can create Docker containers using the Container Station user interface. Go to ‘Containers’, click ‘Create’, and select an image from the available registries.

4. Configure Network Settings: Container Station supports multiple network modes and VLAN for flexible deployment. You can manage these settings according to your need.

5. Manage Containers: After creating your Docker containers, you can manage them through the Container Station interface, where you can start, stop, and configure your containers as needed.

For detailed instructions and the latest updates, refer to the official QNAP Container Station guide. It provides comprehensive information on using Container Station, including creating, managing, and deploying Docker containers.

You should be able to run syncthing in docker on qnap. Which model and software version is it?

Keep in mind that sync is not a backup, neither is RAID.

If you do multiple passes you can alleviate some of the downsides of low bitrates. You can always easily spot it in dark areas. I despise watching space movies or shows on streaming services because of the resulting excessive banding artifacts.