-
Notifications
You must be signed in to change notification settings - Fork 658
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Modify deployment scripts to serve static files from web service #377
Modify deployment scripts to serve static files from web service #377
Conversation
### Motivation and Context <!-- Thank you for your contribution to the chat-copilot repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> this PR prepares the frontend for #377 and removes the need for any AAD configuration environment variables. ### Description - removes `REACT_APP_AUTH_TYPE` and all variables starting with `REACT_APP_AAD_` - calls the `/authConfig` endpoint when the app first loads and if needed, renders the `MsalProvider` using the fetched config. - updates workflows and deployment scripts accordingly <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [X] The code builds clean without any errors or warnings - [X] The PR follows the [Contribution Guidelines](https://github.com/microsoft/chat-copilot/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/chat-copilot/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [X] All unit tests pass, and I have added new tests where possible - [X] I didn't break anyone 馃槃
the docs could be updated to reflect the new deployment steps sk-frontend-deployment Also is it required to create 2 separate app registrations, now that both frontend & backend is served from within one appservice |
@raj-microsoft You still need 2 app registrations. The frontend files can be hosted anywhere independently from the backend. They are now hosted by the backend by default to reduce the number of moving parts and to reduce the number of steps required to get to a functional Chat Copilot deployment. Thank you for pointing out the disconnect with the documentation on learn.microsoft.com. I will go and fix that. |
Motivation and Context
This change enables having a generic single package containing both backend and frontend that can be deployed using the "Deploy to Azure" button.
It also reduces the complexity and cost of deployments.
Description
Contribution Checklist