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.

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

[6.x] Configurable of Laravel dusk routes enhancement #774

Merged
merged 5 commits into from
May 13, 2020
Merged

[6.x] Configurable of Laravel dusk routes enhancement #774

merged 5 commits into from
May 13, 2020

Conversation

dmitryuk
Copy link
Contributor

@dmitryuk dmitryuk commented May 13, 2020

Continue declined PR #772
Resolve an issue #773

The issue I mean is Laravel dusk can't work with a separated backend and frontend.
For example, frontend (SPA) is located on "example.com", backend - "api.example.com".
Since Dusk's API internal methods will call example.com/_dusk/... methods, it is not reachable on this service.
So I searched a way how to configure it, but currently it is not possible. Routes are hardcoded.

I improved the PR by adding config file, so in future it can be used in future for resolving issues like #393

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants