Trying to avoid a container with a full fledge nginx, lighthttpd container to serve boot images through http.
I just dicovered the file sharing, back to home files I that would work.
But, I don’t need to share them externally and http would be a little faster for iPXE to load my images than https minimizing morning bootstorm. Avoiding opening my images externally.
What would you suggest for my scenario.
Rock
The traffic to BTHF ("Share" option in Files) might be local, not via internet. While it will resolve the public IP, that should not leave your router/network. Now BTHF can run in "proxy mode" if the router is not a gateway, or network is behind CGNAT/double-NAT'ed... in which case, your right it would go out to come back in.
But there is no built-in file server feature, so you can't just put a file and have it served via HTTP. Now you can use Branding Kit to add file, or perhaps abuse /ip/hotspot, to "add a file" but this is more trouble than running a small container
You can use busybox's httpd in container, which is very slightly smaller than lighttpd. But in the doesn't matter category since lighttpd is pretty "light" too. For an example using 7.22 /app feature, see: V7.22beta [development] is released! - #353 by Amm0
I am on the waiting list also for just a share directory from the built in web server(webfig)...
Would be a nice little device to plug in usb drive and pxe boot from and share some iso's with memdisk. Have built this on a raspberry på before, and it's working great. But sadly the RPI has only 100Mbit ethernet interface. Have tried to pxe boot iso's with ftp on Mikrotik but the transfer rate is not great. So please just add a folder to the webfig thats you can point to some directory on the device, /flash.