A2. Using Your Own D-BAS Instance

Instead of the fresh, and build in D-BAS instance you can use your own. You can change the D-BAS software that is used (in case you added custom features, or want to use a certain other version than the supplied) or you can just exchange the database used, respectively mount your database data inside the database-image.

To do so you only need a few steps.

Changing out the D-BAS Image itself

Search for the dbas: line in the docker-compose.yml.

Here you can use the image: command to specify your D-BAS image if you have it as a docker container. In this case you need to also to remove or change the bound volumes if applicable. Furthermore you can change the used environment file by changing the env_file variable.

Another method would be to exchange the dbas directory in your eden directory with the new instance. In this case you need to customize the

- ./dbas_development.env:/dbas/development.env

line. Alternatively rename your environment file to dbas_development.env and drop it into the eden directory.

Using own database for D-BAS

To use your own D-BAS compatible or preexisting database you can customize the corresponding dbas-db service inside the docker-compose.yml.

Either replace the build command with the image command and your corresponding image, and/or change the mounted volumes which presist the database.
The persisted data is usually found in the /var/lib/postgresql/data directory inside the default D-BAS database image. You can, for example, extend the volumes command with:

- ./path/to/your/persisted/db/data:/var/lib/postgresql/data