I’d say 9/10 aren’t doing proper backups given most people don’t actually do DR runs and verify whether they can fully recover from their backups. If you don’t test your backups, you don’t have backups!

Which containers do automatic DB backups? Normally the database is a separate container, unless the app is using SQLite. Is there a MySQL or PostgreSQL container that does automated backups?

Where’s the MySQL option? Some of my servers are running MySQL instead of MariaDB because it allowed binding to multiple IP addresses (although I think Maria has implemented this now), and some query plan optimizations were implemented in MySQL but not MariaDB.

You still need to know what database system is being used in order to make backups of the database. You can’t just snapshot or backup the data directory while a database is running, because you might end up with an inconsistent state that won’t restore properly. You need to either stop the DB before doing the backup, or use the relevant DB-specific tools to perform a backup.

I’m a C# developer and run .NET apps on Linux all the time. I usually work on CLI and server apps, but recently released my first Linux desktop app written in C#: https://flathub.org/apps/com.daniel15.wcc

Even before .NET Core, I was using Mono to run C# apps on Linux. There used to be quite a few GNOME apps written in C#.

There’s .NET and then there’s .NET Core which is a mere subset of .NET.

Nope. The old .NET Framework has been deprecated for a long time. The latest version, 4.8.1, is not very different to 4.6 which was released 10 years ago.

The modern versions are just called .NET, which is what .NET Core used to be, but with much more of the framework implemented in a cross-platform way. Something like 95% of the Windows-only .NET Framework has been reimplemented in a cross-platform way.

The list of .NET stuff that will actually run on .NET Core (alone) is a barren wasteland.

All modern .NET code is built on the cross-platform framework. Only legacy apps used the old Windows-only .NET Framework.

If you get the free community version of Visual Studio and create a new C# project, it’ll be using the latest cross-platform framework. You can even cross-compile for Linux on a Windows system.

Thanks, this is a good insight.

That’s a very old way of thinking of things. C# has been cross platform for a long time.

Almost everything ever written in C# uses Windows-specific APIs

Not really. Most C# apps use .NET (since the framework and standard library is quite feature-rich) rather than direct Win32 calls, and .NET is cross-platform. A lot of web services are written in C# and deployed to Linux servers.

basically no one installs the C# runtime on Linux anymore

You can compile a C# app to a single executable that doesn’t require the framework to be installed.

Are you running Jellyfin, the *arr suite, slskd, or Technitium DNS? They’re all written in C#.

Yeah it’s definitely not possible to reach 50MB with a Node.js Docker image, but <150MB should be doable with a distroless base image + compiling the app into one JS file (for example, using Parcel or esbuild).

It’s possible to reach ~50-60MB Docker image with a C# app. Rust and Go definitely produce more compact binaries though.

This makes sense! You get the same advantage if the app uses Go or C# though, and both of those can compile to a single statically-linked executable too.

if it were written in NodeJS or Python or something I’d be less interested.

Does it matter if it’s running in Docker and the container is lightweight (say less than 50MB), though? I like apps being written in a language I know well so I can contribute if needed, but other than that, I mostly treat a Docker image as a black box.

Looks like a good project, but I genuinely don’t quite get why Rust projects feel the need to advertise “written in Rust” as a feature. Do you find that a lot of users care which programming language your app is written in? Does it help with finding contributors?

I don’t know which programming language most of my self-hosted apps use, and I don’t mind since they all work well and do their job.

The book was written to sell Windows Home Server. https://en.wikipedia.org/wiki/Windows_Home_Server

unless microsoft finally realizes rootkits are a bad thing.

Isn’t that what happened after the CrowdStrike issue? https://www.theverge.com/2024/7/26/24206719/microsoft-windows-changes-crowdstrike-kernel-driver

Windows Store is useful for less sophisticated users though. It’s dangerous teaching non-computer-illiterate people to install apps by downloading random EXE files.

I was one of those cool 90’s kids who hated Clippy, and I am still just as immature.

I always liked the red ball and the wizard more than Clippy anyways.

Isn’t the IoT version missing some features?

The real fix is to switch to Linux.

Also, what’s wrong with Clippy?

Install Nginx, add autoindex on; to the default site config, throw the files into /var/www/html or whatever default folder it uses, and delete the default index.html file. If you need to do it via Docker then use the official Nginx image https://hub.docker.com/_/nginx

You could also just share the files via SMB. Easy to use on a PC - you could configure their computers to mount the share as a network drive on boot (e.g. R:, for recipes). Not sure about other phones but the built-in files app on my Galaxy S25 Ultra supports SMB too.

I use Plex for music just because they currently have the best app (Plexamp). My Plex server is mostly just music, and TV shows I record off an antenna using HDHomeRun.

When we start decent seeing vehicles at a decent price again

These exist, they’re just not in the USA. Look at what companies like BYD and Xiaomi are doing in practically every developed country except the USA. The entry-level BYD Dolphin is just under AU$30k (US$19k) in Australia, including taxes. Xiaomi have a sports car for around US$40k.

A lot of apps still use legacy Windows APIs that don’t understand very long paths. Those APIs have been deprecated for maybe 15 years or more, but developers are lazy. Microsoft can’t add support for long paths to the old APIs because they use a fixed buffer size (which means that only a certain amount of memory space is available for the path, and increasing it would break the apps that rely on that). They can’t totally remove the old APIs because every app that uses them would break.