h5ai – modern HTTP web server index
larsjung.de
larsjung.de
It also has ACL and can be used either as a listing directory or serving html files.
I love it :).
Only caveat so far: it doesn't like being proxied under a sub folder (https://example.com/dufs/).
I was fed up with nextcloud and replaced it with syncthing (for laptop/desktop) + dufs + wedav for mobile access, all hosted on a pi@home, accessed through a wg VPN.
"Works for me!" without any /'s, eg.
--path-prefix dufsThe idea was that you slap the index.php in a single location and then symlink it to folders.
All icons were included in the source so it was just one file. I think it's still working on an abandoned shell of mine somewhere =)
PHP just slapping the code into the public directory always makes me nervous, especially when this has an upload feature.
> Add /_h5ai/public/index.php (note the leading slash!) to the end of the default index-file list. In this way h5ai will manage all directories in and below DOC_ROOT that don't have a index file.
I think I found a bug though, and made a video of the screencast and out it at here: https://photos.app.goo.gl/UxoRyVgcAX497dii9
I click on “search and filter”, it get selected, another click, it navigates to it. And on the new page, “archive.zip” is selected, simply because it is on the same position where “search and filter” was.
Thanks.
I understand that https://larsjung.de/h5ai/demo/special%20chars/screenshot.jpg is a link to the actual file itself, but it would still be nice to have the preview itself be linkable - and be navigable via the back/forward buttons, browser history etc.
So how about using a fragment hash here? https://larsjung.de/h5ai/demo/special%20chars/#file:screensh... (that's the directry URL with #file:screenshot.jpg at the end of it) - that way the back/forward buttons could work, the preview would be linkable and there wouldn't be confusion with the actual URL to the file.
clicking a file and a big spinner appearing. hitting back button to go back up a few folders, spinner never goes away, etc.
And before that, it felt to me it had gotten mostly pigeonholed for a while as a marketing term to refer computer opponents in games.
Before that, we are finally at its original broader, expansive meaning (the same meaning it's always had in research).
But maybe I've missed a few steps.
The project was last updated 3 years ago. Seems like an unintentional naming collision.