Feat - development server reverse proxy #168
Draft
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.
Purpose
Companion to osf.io PR #11224.
Enables osf.io (localhost:5000) to act as a reverse proxy for the angular-osf dev server (localhost:4300) during local development.
Key points
1 .
baseHref
Resource URLs need to start with
/angular_osf
to be properly proxied.baseHref
is set to/angular_osf/assets/
, ensuring that URLs such as/@vite/client
resolve correctly.2 . Cookie authentication
Although a dedicated login UI is not included, the app now reads the standard auth cookies. If the user is already authenticated, their username appears in the top-right corner. One possible verification flow is as follows:
PRIMARY_WEB_APP="ember_osf_web"
(osf.io/website/settings/local.py
).http://localhost:5000
and sign in viaember-osf-web
.PRIMARY_WEB_APP
to"angular_osf"
and restart theweb
service.http://localhost:5000
;angular-osf
loads and displays the logged-in user.