v8go VS certmagic

Firstly, I used rogchap/v8go to execute JavaScript in a Go environment. I listed other options below.

Now the only issue I see is that someone who can't be bothered to install PHP and composer will probably not want to install node and npm either. If you could somehow run WASM inside an executable file (maybe something written in Go with https://github.com/rogchap/v8go ? Or an Electron App ?), all you'd need to do is download the executable file on any computer and double click it to start serving a Laravel project.

I only browsed for a wee bit, so take this with some salt, but it _looks_ like the framework is running a JS VM isolate alongside the Go server struct[1], which gets called with whatever script file is being rendered. Since it looks like the render files are, at least in the case of Svelte, individually compiled JS files that are SSR rendered via the V8 isolate, I _believe_ you're correct that there is no CSR (though there might still be JS-hydrated code if the Svelte component included something involving an interactive component).

I think the idea is to ingest a JS "template" and spit out the rendered HTML+JS, kind of like traditional SSR templates, but it could be possible to shoe-horn in an entire client-side router that gets initialized as a DOM object somewhere.

[1] https://github.com/rogchap/v8go

https://github.com/rogchap/v8go is a viable option these days as well.

Plenti is a simple open source Static Site Generator (SSG) with a Go backend and Svelte frontend. Jim picked Golang because it is simple, quick and has the ability to generate a binary that can be run on any machine; and Svelte, well, for one, “Svelte is so hot right now” and also because of the power it gives developers to write simple HTML and CSS to create websites. Merging these two technologies was not an easy task, but with V8Go binding the two together, it’s a marriage that works.

Now, I serve TLS directly from the application and was able to make it all work with Certmagic.

For deployment, you may not need a reverse proxy with Nginx or the likes. Certmagic will make HTTPS a breeze. Also makes it possible to handle multi-tenant SaaS domains SSL provisioning. While not the easiest, it was much easier than trying to do it at the reverse proxy and cheaper than doing it with Cloudflare's SaaS service.

If you don't want to move certificate management to a different service, use CertMagic in your app.

With certmagic its done completly automatic using letsencrypt: https://github.com/caddyserver/certmagic

The project is also a boon for devs. The certmagic library0 makes it trivial to add Let's Encrypt support to any Golang web server code.

Because Lego maintainers wouldn't budge when Caddy needed changes made to increase ACME reliability. Matt wrote his own implementation https://github.com/mholt/acmez and started using that in Caddy soon after. There's a deeper explanation here: https://github.com/caddyserver/certmagic/issues/71

That said, I would use https://github.com/caddyserver/certmagic to manage you SSL certs.

I terminate SSL in GO (less moving parts to manage), and use https://github.com/caddyserver/certmagic to provision and renew my certs.