self-serve? about miniserve HOT 3 OPEN

That would be pretty easy to implement I think but would it be something that's actually useful? I suppose if you wanted to share miniserve you could just share the dir it's in. It's also not a given that the OS that's accessing your host is compatible with the binary that you're running. Can you illustrate your use case for me?

However, I do like a self information page.

from miniserve.

Can you illustrate your use case for me?

It just seemed like a self-evident implication of the "single static binary" aspect. I could make one up, such as hosts that are not connected to the internet and want to get going, but I don't have any particular one in mind. It seems like part of the basic concept is to be useful for general, quick, unforseen circumstances, maybe where other more useful connectivity (like ssh) doesn't exist or needs more setup (credentials).

I suppose if you wanted to share miniserve you could just share the dir it's in. It's also not a given that the OS that's accessing your host is compatible with the binary that you're running.

True, but that's why I suggested a convenience option to serve the redirect and the file with the longer name (so the thing you wind up downloading is clearly OS specific, and you can spot mismatches).

However, I do like a self information page.

That would work too instead of a redirect - a bit of self information, potentially with a link to the binary as well.

from miniserve.

Since this wouldn't add too much complexity and I can see a limited case of uses where this would be convenient to have, I'd accept a PR that'd add this.

Do we just want to stick all of this in the footer of every generated page or should it rather be its own page, linked to by the footer?

from miniserve.