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

Add proxying to front-end development server. #442

Merged
merged 6 commits into from
Mar 29, 2018
Merged

Add proxying to front-end development server. #442

merged 6 commits into from
Mar 29, 2018

Conversation

wbuchwalter
Copy link
Contributor

@wbuchwalter wbuchwalter commented Mar 7, 2018

(Dependant on #441)

Simplify the development workflow of the dashboard.
In development, all requests from the frontend (running on port 3000) will be automatically proxied to :8080/tfjobs/ where the backend dev server should be running.

This avoids needing to make manual modifications to services.js when developing locally.


This change is Reviewable

@coveralls
Copy link

coveralls commented Mar 7, 2018

Coverage Status

Coverage remained the same at 45.323% when pulling a7713db on wbuchwalter:dash-dev into b72f47e on kubeflow:master.

@jlewi
Copy link
Contributor

jlewi commented Mar 8, 2018

Not sure @ankushagarwal or @gaocegege are JS experts. Who are the other knowleadgeable people about javascript/react?

I'll open an issue to create a suitable owners file.

@gaocegege
Copy link
Member

I know little about JS but I think @jimexist may know more.

@wbuchwalter
Copy link
Contributor Author

wbuchwalter commented Mar 8, 2018

If you want to know more see: https://github.com/facebook/create-react-app/blob/master/packages/react-scripts/template/README.md#proxying-api-requests-in-development

Note that this doesn't affect production in any way.

@jimexist
Copy link
Member

jimexist commented Mar 8, 2018

/lgtm

let host = "";
import { getHost } from "./utils";

const host = getHost();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this gets used anywhere?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, see line 6 of the same file for example.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok sorry missed the deleted empty string line.

@ankushagarwal ankushagarwal removed their request for review March 8, 2018 14:49
@gaocegege
Copy link
Member

gaocegege commented Mar 9, 2018

@wbuchwalter The label do-not-merge may not work since it is not added by the bot, you could use /hold to freeze the PR and use /hold cancel to cancel it.

@gaocegege
Copy link
Member

/hold

@wbuchwalter
Copy link
Contributor Author

@gaocegege Ah thanks :)

@wbuchwalter
Copy link
Contributor Author

/hold cancel

@jlewi
Copy link
Contributor

jlewi commented Mar 28, 2018

/lgtm

@k8s-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Jimexist, jlewi

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot merged commit 53cf090 into kubeflow:master Mar 29, 2018
jetmuffin pushed a commit to jetmuffin/tf-operator that referenced this pull request Jul 9, 2018
* dashboard: dev guide

* fix dashboard + proxy issue

* dashboard: move to hash router

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

Successfully merging this pull request may close these issues.

6 participants