This ensures the API uses the same protocol and domain as the frontend,
preventing mixed content blocking in staging/production environments.
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
- Update CORS config to allow all origins (wildcard first) for better staging support
- Change API fetch base URL from absolute to relative (/) to prevent mixed content blocking
- Add detailed logging in music create page for better debugging
- Update .env.example with better NEXT_PUBLIC_BASE_URL documentation
- Add MUSIK_CREATE_ANALYSIS.md with comprehensive error analysis
Fixes ERR_BLOCKED_BY_CLIENT error when creating music in staging environment
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
- Add serverExternalPackages for @elysiajs/static and elysia to prevent
webpack from bundling dynamic imports that cause Html prerender error
- Use output: standalone for proper Docker deployment
- Comment out NODE_ENV=development in .env.example to avoid conflict
with next build which requires NODE_ENV=production
- Set NODE_ENV=production before build step in Dockerfile
- Update runtime stage to use standalone output structure
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
