-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Deployment docs extras #2443
base: main
Are you sure you want to change the base?
Deployment docs extras #2443
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Love the docs. Great work!
If you want to set up a custom domain for your Wasp app, you can do it for both the client and the server. | ||
|
||
You point users to visit your client app, so setting up the custom domain for the client is the impactful part. Setting up a custom domain for the server is optional, but it can be useful if you'd like to hide the actual server domain from the users. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The first sentence was a little weird to me, maybe we can turn it around:
The important part is setting up the custom domain for the client - that's what your users visit from their browsers.
You need to set the environment variables so Wasp configures the app correctly (for example, for CORS to work correctly). | ||
|
||
**For the client**, you need to set the `REACT_APP_API_URL` environment variable to the **server domain** when [building the client](./env-vars.md#client-env-vars). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we can have two subsections: client and server instead of "For the client" and "For the server"
This PR will: