devd VS Caddy

Your technique is one I would turn towards as a developer who understands HTML/CSS flow so much better than I do any typesetting tool. I actually use a very similar technique for managing my CV and generating invoices for clients; I have a little "static site" generator I've written that takes JSON, throws it through a templating engine, and spits out HTML files. I then host a server in the output folder and print-to-pdf directly from there. This approach seems quite rare; I don't think enough people appreciate just how flexible CSS is or its support for common print-related tasks.

There are plenty of solutions to that specific problem. Nowadays, I only work on Nuxt/Next/Astro projects that come with hot reload out of the box so I don't have a need for it anymore, but I have used https://github.com/cortesi/devd a lot in the past, with much success.

A no-install solution would be to use the "workspace" feature of Chrome's Dev Tools:

1. Open your .html file in Chrome.

2. Open the Dev Tools.

3. In the "Sources" tab, activate the "Filesystem" sub-tab.

4. Click on "+ Add folder to workspace" and choose the directory containing your .html and .css files.

5. Edit the .css file with autocompletion and live preview.

6. Save your work so that it is synchronized with your filesystem.

In action: https://i.imgur.com/slcSt9X.gif

Try https://github.com/cortesi/devd

This pair of tools do both front-end and back-end live reloading with a small amount of config: https://github.com/cortesi/modd https://github.com/cortesi/devd

In tandem with https://github.com/cortesi/devd I've found it a good setup for web development.

Modd watches file changes and rebuilds, while Devd enables livereload, letting me make changes in my text editor and then see the rendered changes in the browser, side-by-side, in near real-time.

This is for go web development but I'm pretty sure these two tools are language-agnostic.

My favourite is https://github.com/cortesi/devd

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/