Development workflow

All commands are run from the root of the repository. For explanations of the various commands used in the workflow, see Workflow Explanations

Starting development:

Make sure your volume is correctly mounted. On Windows you will most likely need to check out Issues with volume mounting after every restart.

When Docker and Kubernetes starts, it should be up and running. If the volume mounting crashed (check using kubectl get pods and look for failed statuses), run kubectl delete pods --all and Kubernetes will recreate and restart all pods.

Changing a node-service without adding new dependencies to package.json:

• Make your changes
• kubectl delete pod <servicename>

Changing a node-service that adds a new dependency

• Make your changes
• docker build <path-to-dockerfile> -t microservices/<servicename>
• helm upgrade <deployment name> -f Infrastructure/kubernetes/charts/default/values.dev.yaml -f Infrastructure/kubernetes/charts/default/local.yaml ./Infrastructure/kubernetes/charts/default/

Changing a .Net-service without adding new nuget-packages:

• Make your changes
• App will hot reload

Changing a .Net-service that adds new nuget-packages:

• Make your changes
• docker build <path-to-dockerfile> -t microservices/<servicename>
• helm upgrade <deployment name> -f Infrastructure/kubernetes/charts/default/values.dev.yaml -f Infrastructure/kubernetes/charts/default/local.yaml ./Infrastructure/kubernetes/charts/default/

Adding a new service:

• Add the new service
• docker build <path-to-dockerfile> -t microservices/<servicename>
• helm upgrade <deployment name> -f Infrastructure/kubernetes/charts/default/values.dev.yaml -f Infrastructure/kubernetes/charts/default/local.yaml ./Infrastructure/kubernetes/charts/default/