Skip to main content
Version: 5.x

Configure Auto-Reloading

There are certain use cases where you want to rebuild and redeploy the whole application instead of using the file synchronization and hot reloading. DevSpace provides you the options to specify special paths that are watched during devspace dev and any change to such a path will trigger a redeploy.

Auto-reloading can be configured in the dev.autoReload section of devspace.yaml.

images:
  backend:
    image: john/devbackend
  database:
    image: john/database
deployments:
- name: app-backend
  helm:
    componentChart: true
    values:
      containers:
      - image: john/devbackend
- name: custom-manifests
  kubectl:
    manifests:
    - manifests/
    - more/manifests/
dev:
  autoReload:
    paths:
    - ./package.json
    - ./important-config-files/*
    images:
    - database
    deployments:
    - custom-manifests

Take a look at the redeploy-instead-of-hot-reload example to see how to disable hot reloading at all and enable redeployment on every file change instead.

Configuration​

paths​

The paths option expects an array of strings with paths that should be watched for changes. If a change occurs in any of the specified paths, DevSpace will stop the development mode, rebuild the images (if the context has changed), redeploy the application and restart the development mode (sync, port-forwarding, log streaming etc.) afterwards.

images​

The images option expects an array of strings with image names from the images section of the devspace.yaml. If a change occurs to the dockerfile or to one of the files within the context of this image (if its context has changed), DevSpace will stop the development mode, rebuild the images, redeploy the application and restart the development mode (sync, port-forwarding, log streaming etc.) afterwards.

deployments​

The deployments option expects an array of strings with names of deployments from the deployments section of the devspace.yaml. If a change occurs to any of the files that belong to this deployment, DevSpace will stop the development mode, rebuild the images (if the context has changed), redeploy the application and restart the development mode (sync, port-forwarding, log streaming etc.) afterwards.

Manifest Deployments

For kubectl deployments, DevSpace watches for all paths configured under manifests.

Helm Chart Deployments

For helm deployments, DevSpace watches for changes in the valuesFiles or changes in the chart path of a local chart (configured as chart.name).