-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
[docs] Fix AI assistant API URL #17745
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
Conversation
Thanks for adding a type label to the PR! 👍 |
Deploy preview: https://deploy-preview-17745--material-ui-x.netlify.app/ Updated pages: |
API is still running from the branch. I will work to have https://github.com/mui/mui-private/pull/695 merged. Then we can remove the DNS records and update the docs. @joserodolfofreitas I assume no one started building their own service, so it is safe to do it without redirects from the old subdomain? |
@arminmeh What's the blocker to have the AI backend run from a master branch?
I think so. But yeah, we need to update https://dashboard.render.com/web/srv-cvvovgc9c44c73f6cit0/env ![]() |
@oliviertassinari no blockers. I will move this on top of my queue. Should be finished soon. |
@arminmeh Alright, at least, from an docs standpoint, I assume that we can move forward with this PR since it's the same URL used by the live demo. |
This seems wrong, no? Only https://dashboard.render.com/web/srv-cvvovgc9c44c73f6cit0 runs in production.
I guess we can delete this too? https://app.netlify.com/teams/mui/dns/mui.com
On this page:
The "avoid" feels very strange. Either it's a "must" or this section shouldn't be here in the first place. I would imagine that it should be "must" today, and not be here once we allow developers to whitelist origins.