Skip to content

devspace

Since devspace should be able to do a complete install recursively through dependencies this will be the main deployment section to use.

The tree structure will be :

directory tree
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
doc
cheatsheet
www
klopt
├── base
│   ├── backend-build
│   │   ├── docker-compose.yml
│   │   ├── Dockerfile
│   │   ├── makefile
│   │   └── osrm-backend
├── planner
└── solver
    ├── apache.yaml
    ├── backend
    ├── db

doc and cheatsheet are two separate directories and they are simply deployed with devspace build; devspace deploy. klopt is divided into these steps/directories :

  • base : one time deployments
  • base/backend-build : a builder image for the solver (for jenkins mainly)
  • base/db : database deployment for bag and klopt
  • solver : the backend code
  • solver/lkh : the solver code
  • solver/backend : the backend code
  • planner: frontend website

base

Base should contain the building blocks only installed once and updated very rarely. For instance :

  • backend-build : the docker image that is used to build the backend.
  • ingress : the routing and TLS handling for kubernetes
  • network-pvc : the volume used by backend and db containers
  • db : all database deployments, bag and klopt

solver

images for the backend such as :

  • db : the database image for web and bag
  • lkh : the solver code
  • backend : the backend application