Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

26138 handle api proxying using next #627

Open
wants to merge 10 commits into
base: dev
Choose a base branch
from

Conversation

PoffM
Copy link
Contributor

@PoffM PoffM commented Jan 6, 2022

No description provided.

PoffM and others added 10 commits January 6, 2022 15:29
-Moved API reverse proxying to Nextjs API route function.
-Moved keycloak confiug to API route.
-Moved internet explorer check to a Nextjs middleware function.
-Removed dev Caddyfile.
-Updated @rehooks/local-storage version so it works with Nextjs pre-rendering now, removed old workaround.
-Updated Dockerfile to work with the new Next.js output.
Updated nextjs to 12.0.8
-Updated other react/next related dependencies.
-Fixed ClientSideJoiner error.
- Dockerfile is currently being worked on, building and installing dependencies are now done directly from there.
- AccountProvider has been simplifed to use enviroment variables. This also removes that keycloak message in the console.
- Dev and start scripts have been added to the package.json, now use the nextjs commands.
- Reverted back the docker and keycloak changes.
- Working on finding a next version that fixes the crash when proxy cannot be resolved.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants