Explore >> Select a destination
|
You are here 
|
robert.kra.hn | ||
| | | | |
hoverbear.org
|
|
| | | | | Fitting the pieces together for pleasant errors and logs. | |
| | | | |
blog.sylver.dev
|
|
| | | | | In this episode, we'll extend our server to serve static files. We'll also refactor our code to support connection reuse, and implement a graceful shutdown mechanism. If your didn't follow the previous episode, you can find the code on GitHub. As we ... | |
| | | | |
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: | |
| | | | |
glama.ai
|
|
| | | Search, compare, and connect to thousands of MCP servers. Glama indexes, scans, and ranks servers based on security, compatibility, and ease of use. | ||
