Problem: ASP.NET Core static files middleware may not handle symlinks correctly,
causing blazor.web.js to be served as a 21-byte stub instead of the full 60KB file.
This caused 'SyntaxError: Invalid or unexpected token' in browser.
Solution: Replace symlink with actual file copy in deploy_gb.sh:
- cp blazor.webassembly.js blazor.web.js (+ .gz and .br variants)
This ensures both filenames are actual files that the static files middleware
can properly serve.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Problem: ASP.NET Core 10 WASM runtime file is named blazor.webassembly.js but
Blazor pages still reference blazor.web.js, causing 404 Not Found errors and
complete failure to load admin UI.
Solution: In deploy_gb.sh, create symlink before starting the app:
ln -s blazor.webassembly.js blazor.web.js
This allows both filenames to work, ensuring backward compatibility.
Result: WASM runtime loads correctly in deployed environments.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
- Add ConnectionStrings__Default env var to deploy_gb.sh for production deployment
- Add DOTNET_PRINT_TELEMETRY_MESSAGE=false to suppress telemetry
- Update E2E tests to support env vars (E2E_BASE_URL, E2E_ADMIN_USERNAME, E2E_ADMIN_PASSWORD)
- Fixes 'Missing connection string' error on new deployments
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
kjh2064