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.

Sign up for GitHub

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

clarifying doc #2481

Merged
merged 1 commit into from
Aug 23, 2023
Merged

clarifying doc #2481

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion site/_includes/docs/_hosted-backend-warning.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@ When developing against a FusionAuth Cloud instance with a `.fusionauth.io` addr

To work around this, you can:

* develop locally (`localhost` will work).
* develop using a local FusionAuth instance, so both your webapp and FusionAuth are running on `localhost`.
* set up a lightweight proxy to ensure both servers are the same domain.
* stand up a barebones backend with a more liberal cookie policy: [here's an example](https://github.com/FusionAuth/fusionauth-example-react-sdk/tree/main/server).
* set up a [custom domain name for the FusionAuth Cloud instance](/docs/v1/tech/installation-guide/cloud#updating-with-existing-custom-domains) (limited to certain plans).
Expand Down