-
Notifications
You must be signed in to change notification settings - Fork 1
Simplified Development Setup
We observed that the standard deployment to a local minikube cluster using garden deploy
takes quite some time to complete. Also the garden dev
command did not help us out because we had different issues (e.g. too many open file handles). Therefore we use a different for most of our development on the frontend and backend components. We only deploy the relevant part to the kubernetes cluster, namely the scheduler, the Postgres database. The frontend and backend will be started directly on your local machine and not in the cluster.
We tested this setup under macOS and Ubuntu with minikube v1.14.2
. Under Ubuntu simply run minikube start
. Under macOS run minikube start --vm=true
To deploy the needed components and setup the port-forwarding run the script deploy_dev.sh
.
create a python virtualenv, activate it and install the requirements with pip install -r services/python-images/requirements.txt
go to the directory services/python-images/src
and start the dev server with run_dev_server.sh
go to the directory services/frontend-image/src
and run yarn start
- Home
- Setup
- API Documentation
- Data model
- How to...
- ...add a new remote database
- ...create migrations
- ...develop locally
- ...simplified dev setup
- ...deploy on kubernetes (internal)
- ...monitor the cluster
- ...fix expired K8s certificates
- ...add new dependencies
- ...rebuild base image
- ...add a new algorithm in R
- ...add support for new language
- ...add a new node to Kubernetes cluster
- Coding Conventions
- Roadmap
- Ownership