If you wish to migrate your containers from DeployBot's build pipeline to DeployHQ's, and you don't want to apply your runtime configuration permanently on a project basis, a straightforward way to do so is to create and add a `.deploybuild.yaml` file in your repository, which has details on the build runtimes you wish to use with your builds. 

This has a slight caveat: your runtimes will apply your `.deploybuild.yaml` configuration as long as the file is within your repository, on the root path of your repository deployment directory.

### Mapped templates for DeployBot's base containers to .deploybuild.yaml

Below, you can find the default containers available in DeployBot, mapped to base `.deploybuild.yaml` files. If needed, you can add more specifications to these by following the YAML structure, and adding the runtimes with their associated major version.

#### Default DeployBot Ubuntu image

```yaml
build_languages:
  - name: "node"
    # currently available versions: 21, 20, 19, 18, 17, 16, 15, 14, 12, 10, 9, 8
    version: "18"
  - name: "php"
    # currently available versions: 8.3, 8.2, 8.1, 8.0, 7.4, 7.3, 7.2, 7.1, 7.0 
    version: "8.0"
```

On top of these runtimes, you can add your preferred versions for `.NET`, `GO`, `Java`, `Python3`, `Python`, `Ruby`, `Composer` and `PhantomJS` by following the same structure as the one above.

To see the full available version list for each runtime, and modify permanently this configuration, go to your DeployHQ project, under `Build Pipeline >> Build Configuration`.

For more information on what can be done with a `.deploybuild.yaml` file, and its benefits, feel free to check <a href="https://www.deployhq.com/support/build-pipelines/deploybuild-dot-yaml" target=blank>its dedicated article</a>.