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

Providing app/api uri should prevent the emulator from starting its own #17

Closed
aaronpowell opened this issue Sep 28, 2020 · 1 comment · Fixed by #19
Closed

Providing app/api uri should prevent the emulator from starting its own #17

aaronpowell opened this issue Sep 28, 2020 · 1 comment · Fixed by #19
Assignees
Labels
priority: high (P0) High priority scope: cli Issues happened a the ./src/cli level type: enhancement New feature or request

Comments

@aaronpowell
Copy link
Contributor

Let's say I want to run the APP and/or API myself (maybe they run a compiler like TypeScript), I would run the emulator like so:

$> swa --app-uri=http://localhost:3000 --api-uri=http://localhost:7071

But when it starts up, it'll attempt to run its own proxies for those, and in particular the API will fail as the port is already in use.

Since there's no need for these proxies to be run by the emulator, it should skip trying to start them if you provide the uri.

@manekinekko manekinekko self-assigned this Oct 1, 2020
manekinekko added a commit that referenced this issue Oct 1, 2020
@manekinekko
Copy link
Member

I've included this in #19 Now you would do:

$> swa --use-app=http://localhost:3000 --use-api=http://localhost:7071

Would this would for you?

FYI, --app-uri and --api-uri are used to set the URI for the built-in proxies.

@manekinekko manekinekko added priority: high (P0) High priority scope: cli Issues happened a the ./src/cli level type: enhancement New feature or request labels Oct 1, 2020
manekinekko added a commit that referenced this issue Oct 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: high (P0) High priority scope: cli Issues happened a the ./src/cli level type: enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants