filemanager VS Caddy

File Browser

Thanks for sharing. I wasn't aware of dufs and it looks very solid. Fileserver[0] is another popular choice, though it's more GUI-oriented for file operations.

[0]: https://filebrowser.org/

The OnlyOfffice desktop app is a pretty good and free alternative to Microsoft Office Suite. You can simply install it on your local machine for offline access.

OnlyOfffice is also self-hostable as a web app for a cloud alternative to Google Sheets.

Filebrowser is a self-hostable alternative to Google Drive.

There's a pull request open to integrate OnlyOffice with Filebrowser for self-hosted google-drive + google docs.

https://github.com/filebrowser/filebrowser/pull/1420

For strictly local use, Google's Nearby share is technically FOSS but the documentation is basically non-existent and a proper Linux implementation is not here yet. Alternatives aren't hard to find though, with Mint's Warpinator or KDE Connect having worked well for me.

For non-local use (everything out of Bluetooth range), you almost have to trust a third party and it really depends on your use case. Want to send your friend a file or host pictures of your birthday for multiple people to download? For the former magic wormhole works great, for the later you could almost spin up a nextcloud or similar (personally I like https://github.com/filebrowser/filebrowser ). Want to regularly send files from device 1 to device 2? Now classic sync solutions like syncthing become really viable.

If everything else fails, FTP always has your back

I have been looking for a file browser which can run in game mode and is reasonably user friendly for simple file operations (copy/delete/rename, etc). Most people recommend Dolphin. it does work but there are issues: the color scheme looks really weird in game mode. context menu does not like game mode, either. Got file browser working (https://github.com/filebrowser/filebrowser) in game mode, which essentially an Edge app accessing a web server on localhost (running as user service). It took some time to set up but the end result is exactly what I would like to have.

File Browser - For access to the files on my NAS

filebrowser has user management plus sharing capabilities

Filebrowser suppports multiple shares with different expiration dates. It also offers file previews and generates QR Codes for the shares.

NextCloud is great for this, but if we're talking sharing files from your sync'd project collection, I'd probably instead recommend Filebrowser. You can point it to the same data store that syncthing is using and it'll make it easy to share the projects. Note that in order to do this you'll need to open up and expose filebrowser publicly. The simplest way to do this would probably be a cloudflare tunnel and for sharing files like this ad-hoc I don't see any issues with their TOS. For things like SyncThing though you'll still wanna do conventional port forwarding. the DIY approach instead of CloudFlare tunnel would be to port forward, set up a dynamic dns record, and set up letsencrypt certs

No, look at the associated unit test: https://github.com/caddyserver/caddy/blob/c6eb186064091c79f4...

If that test fails we could serve PHP source code instead of having it be evaluated, a major security flaw.

However, it's very unlikely that .NET developers will directly expose their Kestrel-based web apps to the internet. Typically, we use other popular web servers like Nginx, Traefik, and Caddy to act as a reverse-proxy in front of Kestrel for various reasons:

I think that recompiling with upgraded Go will not solve the issue. It seems Caddy imports `golang.org/x/net/http2` and pins it to v0.22.0 which is vulnerable: https://github.com/caddyserver/caddy/issues/6219#issuecommen....

Caddy [1] is a single binary. It is not minimal, but the size difference is barely noticeable.

serve also comes to mind. If you have node installed, `npx serve .` does exactly that.

There are a few go projects that fit your description, none of them very popular, probably because they end up being a 20-line wrapper around http frameworks just like this one.

[1] https://caddyserver.com/

Each app’s front end is built with Qwik and uses Tailwind for styling. The server-side is powered by Qwik City (Qwik’s official meta-framework) and runs on Node.js hosted on a shared Linode VPS. The apps also use PM2 for process management and Caddy as a reverse proxy and SSL provisioner. The data is stored in a PostgreSQL database that also runs on a shared Linode VPS. The apps interact with the database using Drizzle, an Object-Relational Mapper (ORM) for JavaScript. The entire infrastructure for both apps is managed with Terraform using the Terraform Linode provider, which was new to me, but made provisioning and destroying infrastructure really fast and easy (once I learned how it all worked).

So I dug a little deeper and came across this gem: Caddy. Caddy is this fantastic, extensible, cross-platform, open-source web server that's written in Go. The best part? It comes with automatic HTTPS. It basically condenses all the work our scripts and manual maintenance were doing into just 4-5 lines of config. So, stick around and I'll walk you through how to set up an automatic SSL solution with Caddy, Docker and a Node.js server.

Let's use Caddy which can act as reverse-proxy with automatic HTTPS coverage.

Even if it may be simple, it doesn't handle edge cases such as https://github.com/caddyserver/caddy/issues/1632

I personally would make the trade off of taking on more complexity so that I can have extra compatibility.

One of the most heavily used Russian software projects on the internet https://www.nginx.com/blog/do-svidaniya-igor-thank-you-for-n... but it's only marginally more modern than Apache httpd.

In light of recently announced nginx memory-safety vulnerabilities I'd suggest migrating to Caddy https://caddyserver.com/