🐛 fix(web): resolve server connection error by linking SWA to API backend #34
+93
−10
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…kend The frontend was configured to call non-existent custom domains (api.luminous.app, api-stg.luminous.app). The actual API runs on Azure App Service with auto-generated hostnames. Changes: - Update production environment to use relative /api URL - Update staging environment to use relative /api URL - Add staticwebapp.config.json for SPA routing and API configuration - Link App Service as backend to Static Web App via Bicep - Angular assets updated to include SWA config in build output This enables Azure Static Web Apps to proxy /api/* requests to the linked App Service backend, avoiding CORS issues and hardcoded URLs. Applies to: dev, stg, and prd environments
Previously all environments used `npm run build:prod`, ignoring the staging environment configuration. Changes: - Use matrix strategy to build for dev, stg, and prd environments - Each environment uses its appropriate build configuration - Deploy jobs now download environment-specific artifacts Build configurations: - dev: production (uses environment.production.ts) - stg: stg (uses environment.stg.ts) - prd: production (uses environment.production.ts)
Added dedicated environment for deployed dev: - environment.dev.ts with dev-specific WebAuthn rpId - Angular build configuration for dev - npm scripts: build:dev, start:dev - Updated workflow to use dev config for dev deployments Environment configurations: - development (local): localhost:5000 - dev (deployed): /api, rpId: dev.luminous.app - stg (deployed): /api, rpId: stg.luminous.app - production (deployed): /api, rpId: luminous.app
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The frontend was configured to call non-existent custom domains
(api.luminous.app, api-stg.luminous.app). The actual API runs on
Azure App Service with auto-generated hostnames.
Changes:
This enables Azure Static Web Apps to proxy /api/* requests to the
linked App Service backend, avoiding CORS issues and hardcoded URLs.
Applies to: dev, stg, and prd environments