Skip to content
This repository has been archived by the owner on Feb 9, 2022. It is now read-only.

Commit

Permalink
Improve a bit the dev docs, based on my experience (#61)
Browse files Browse the repository at this point in the history
  • Loading branch information
arapulido authored and prydonius committed Feb 13, 2018
1 parent bda522f commit 23afa15
Showing 1 changed file with 6 additions and 1 deletion.
7 changes: 6 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,8 @@ your cluster to your local development server. Run the following commands:
cd ../dashboard
git checkout 2.0
yarn # install any new packages
telepresence --namespace kubeapps --method inject-tcp --swap-deployment kubeapps-dashboard-ui --expose 3000:8080 --run yarn run start
telepresence --namespace kubeapps --method inject-tcp --swap-deployment kubeapps-dashboard-ui --expose 3000:8080 --run-shell
yarn run start # when telepresence returns a shell
```

Now, to access the React app, simply run `kubeapps dashboard` as you usually
Expand All @@ -65,3 +66,7 @@ would:
cd ../kubeapps
./kubeapps dashboard
```

#### Troubleshooting

In some cases, the react processes keep listening on the 3000 port, even when you disconnect telepresence. If you see that `localhost:3000` is still serving the dashboard, even with your telepresence down, check if there is a react process running (`ps aux | grep react`) and kill it.

0 comments on commit 23afa15

Please sign in to comment.