-
Notifications
You must be signed in to change notification settings - Fork 3
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
Test local development of crud-web-apps/jupyter #46
Comments
You can follow the README but a few adaptation where needed. Friendlier steps below:
Frontend# build the common library
cd components/crud-web-apps/common/frontend/kubeflow-common-lib
npm i
npm run build
cd dist/kubeflow
npm link
# build the app frontend
cd ../../../../../jupyter/frontend
npm i
npm link kubeflow
npm run build:watch This will result in a running front-end. Keep it open and open a new terminal to the kubeflow code to start on the backend. Note: These instructions can be made into an executable file for speed.
BackendOpen another cmd window # create a virtual env and install deps
# https://packaging.python.org/guides/installing-using-pip-and-virtual-environments/
cd components/crud-web-apps/jupyter/backend
python3 -m pip install --user virtualenv
python3 -m venv web-apps-dev
source web-apps-dev/bin/activate
# install the deps on the activated virtual env
make install-deps
# run the backend
make run-dev If it explodes, most likely due to one thing. Try this: If it does, make these changes: After running all this, you can navigate to http://localhost:5000/ for a stable Jupyter Management UI When I followed the README in jupyter/frontend and ran ng serve then navigated to http://localhost:4200/, I got many errors and it wouldn't let me connect to any namespace (the default was kubeflow-user). Just to get this to work, I tried to proxy to the backend like we did in our StatCan/jupyter-apis repo by adding the proxy.config.js file in crud-web-apps/jupyter/frontend and ran ng serve --proxy-config proxy.config.js. This then gave me access to the namespaces and notebook servers at http://localhost:4200/. Still testing out this local development to see what will happen if I make changes and add in features, but that's all the progress I've made so far. |
When trying to launch a new notebook server, get the following error:
|
In order to push features upstream, need to be able to locally run the Jupyter Web App in crud-web-apps to see if added features are working properly.
The text was updated successfully, but these errors were encountered: