You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's not clear what the variables mean or how users can configure it to their use cases. For example: INTERNAL_GRAPHQL_URL, EXTERNAL_GRAPHQL_URL, what do these mean and which one would I set to my staging GraphQL url hosted on Digital Ocean?
Expected use cases
I would like to run the started kit locally, but sometimes connected to externally hosted staging Reaction GraphQL server on Digital Ocean.
The text was updated successfully, but these errors were encountered:
In summary, you'd set the .env var for INTERNAL_GRAPHQL_API to the production server's graphql-alpha URL, and then run this:docker-compose run --rm --service-ports web yarn start. Don't forget the --service-ports.
Feature Name
Summary description
Documentation of the .env variables
Rationale for why this feature is necessary
It's not clear what the variables mean or how users can configure it to their use cases. For example:
INTERNAL_GRAPHQL_URL
,EXTERNAL_GRAPHQL_URL
, what do these mean and which one would I set to my staging GraphQL url hosted on Digital Ocean?Expected use cases
I would like to run the started kit locally, but sometimes connected to externally hosted staging Reaction GraphQL server on Digital Ocean.
The text was updated successfully, but these errors were encountered: