imageflow_server should no longer be used

[lilith]

Imageflow.NET Server offers a vastly better experience, performance, and capability set. It contains state-of-the-art hybrid disk caching as well as adapters for blob storage with Amazon, Azure, and others.

Even if I rewrite imageflow_server to not use the outdated/insecure Iron framework, it will never reach performance and feature parity with Imageflow.NET Server. Furthermore, .NET 6 supports compiling to a single executable, so if that turns out to be a strong need we can even do that.

Imageflow.NET Server is easy to deploy using docker, and can be configured with C# (which allows for customization).

imageflow_server is deprecated immediately (it depends on an unmaintained and now-insecure web framework, Iron), and will not appear in Imageflow 2.0.

If you need an exact drop-in replacement, that is possible to do using Imageflow.NET Server - but someone would need to implement the legacy command-line parsing, etc.

If there is enough demand, a version of Imageflow.NET Server can be published that just uses command-line arguments and a .toml config file (although this would limit the feature set).