Explore >> Select a destination
|
You are here 
|
www.shuttle.dev | ||
| | | | |
www.shuttle.rs
|
|
| | | | | Using GPT-4o and Rust to build AI agents in a web service and deploy them | |
| | | | |
nguyenhuythanh.com
|
|
| | | | | In web development and deployment, most software engineers are familiar with either: Separating the built SPA and the backend (Client-Side Rendering), or Return HTML directly from the backend (Server-Side Rendering) I recently (re)discovered 1 that there is a third way: embedding the built SPA into the backend's binary file, and serving it directly. I think this is an elegant approach, as the pros are: Simpler deployment as we only have one binary file in the end Simpler code where we don't have to take into account CORS and the backend endpoint since the frontend and backend are served from the same origin 2 The cons are quite clear: | |
| | | | |
robert.kra.hn
|
|
| | | | | Walkthrough of setting up a full web project that includes the setup for a web server (using axum) and a frontend (using wasm / yew). | |
| | | | |
soundmacguy.wordpress.com
|
|
| | | I thought I was done with SCEP (see parts 1, 2 and 3) but whilst undertaking an exercise looking into using SCEP on some Linux servers (and specifically looking at how it can provide reporting data to SCOMvia a Management Pack), I inadvertently came across a little-documented command line argument for one of its binaries,... | ||
