Implement complete Docker Compose CI/CD setup with optimized builds

- Add multi-stage Dockerfile with dependency caching for both frontend and backend
- Implement Docker Compose configuration with separate frontend/backend services
- Configure Caddy as reverse proxy with proper WASM and static file serving
- Add volume mounting for frontend assets shared between containers
- Optimize build process with staged compilation and workspace handling
- Add debug logging and WASM initialization tracking for production deployment
- Update README with project motivation and "vibe coded" disclaimer

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Connor Johnstone
2025-08-31 17:54:44 -04:00
parent 9b9378477a
commit ed458e6c3a
7 changed files with 143 additions and 55 deletions

View File

@@ -4,7 +4,15 @@
<meta charset="utf-8" />
<title>Calendar App</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<base data-trunk-public-url />
<link data-trunk rel="css" href="styles.css">
</head>
<body></body>
<body>
<script>
console.log("HTML loaded, waiting for WASM...");
window.addEventListener('TrunkApplicationStarted', () => {
console.log("Trunk application started successfully!");
});
</script>
</body>
</html>

View File

@@ -575,6 +575,9 @@ pub fn App() -> Html {
})
};
// Debug logging
web_sys::console::log_1(&format!("App rendering: auth_token = {:?}", auth_token.is_some()).into());
html! {
<BrowserRouter>
<div class="app" onclick={on_outside_click}>