INNER-LOOP.MD

Developer Inner-Loop.

This document describes inner-loop flow while making changes to Azure Vote front-end and back-end application code.

Prerequisite

• DevSpace CLI
• Install Azure CLI
• Install Docker
• Install Kubectl
• Create ACR token
• Login with docker login -u <TOKEN_NAME> -p <TOKEN> <ACR_NAME>.azurecr.io

This repository is using DevSpace as Inner loop framework. DevSpace runs as a single binary CLI tool directly on your computer and ideally, you use it straight from the terminal within your IDE. DevSpace does not require a server-side component as it communicates directly to your Kubernetes cluster using your kube-context, just like kubectl.

DevSpace allows you to store all your workflows in one declarative config file: devspace.yaml. This repository has devspace.yaml for Azure vote App that includes both font-end and back-end.

Inner-Loop Flow

1. Rename .env.template to .env and run source .env for setting config values.
2. Run devspace use context and select kubernetes cluster followed by devspace use namespace <namespace_name>
3. Post making changes to application code run devspace dev to instantly run Azure front-end container along with its dependencies in target cluster. Running devspace dev will also implicitly generate manifest required to run 'Azure Vote App'. To explicitly generate manifest Run devspace run gen-manifest
4. Post running devspace dev, you can access Azure front-end through the port forwarding configuration specified in devspace.yaml e.g http://localhost:8085/
5. Running devspace dev also syncs app files into containers and you can continue making changes to app code without rebuilding image.
6. After the changes are finalized and tested push a new image to Azure Container registry by running devspace build
7. Run devspace deploy to build container image and deploy application to target cluster.
8. Run devspace purge to purge deployed application in target cluster.