Skip to content

Latest commit

 

History

History
62 lines (50 loc) · 4.35 KB

FAQ.md

File metadata and controls

62 lines (50 loc) · 4.35 KB

FAQ

  • Q: when I start the stack, can I make it run just a subset of the available databases? I am not interested in technology xxx and running db3v4l takes up too much cpu/ram/disk! A: sure. The simplest way to do it is to either start only the databases from a given set of vendors, or exclude the databases from a given set of vendors. Example usages:

    export COMPOSE_ONLY_VENDORS=mysql,mariadb,percona
./bin/dbstack start

export COMPOSE_EXCEPT_VENDORS=oracle,mssql
./bin/dbstack start

  • Q: can I customize the configuration of the databases? A: Yes, there is one config file for each db that you can edit, in docker/config. If you change them, you need to restart the docker containers for the settings to take effect, but there is no need to rebuild them

  • Q: what is the exact version of the installed databases? A: for each database that is part of the stack, we strive to install the latest-available minor version for each major version. The minor versions are not set in configuration, but depend on what has been published on Docker Hub by the respective vendors. Depending on the moment that you first build the stack, you might thus get a different minor version, eg. mysql 8.0.14 or mysql 8.0.19. The best way to know the exact version of the installed databases is to run the command ./bin/dbconsole instance:list

  • Q: I dont't like that! Can I pick the exact minor versions of the installed databases? A: Yes, this is possible. In order to specify a specific version for, say, mysql 8.0, you will have to edit the file docker/.env.local and add the line MYSQL_8_0_VERSION=8.0.18. If you had already built the stack before making this change, you will need to rebuild it.

  • Q: can I upgrade the versions of the installed databases to the latest available minor release? A: in order to do so, it is enough to run the dbstack build command with the -u option, which will pull the latest updates to base images from Docker Hub

  • Q: can I make the db3v4l application use an existing database available in my infrastructure besides the self-contained ones? A: yes, as long as the type of database is already supported by the application. In order to add a new database, it is enough to:

    • add a new file docker/config/app/mydb.yml with the definition of the extra remote database in key db3v4l / database_instances
    • add a new file docker/compose/app/mydb.yml where you map the above file to a volume for the worker container
    • test that the worker container can connect to the remote database on the desired port (besides firewalls, the dns resolution might be problematic. If in doubt, test first using IP addresses)

  • Q: can I access the db3v4l databases from other applications running outside the provided Docker containers? I want to do mass data import / export from them. A: it is possible, but not enabled by default. In order to allow it, stop the Docker Compose stack, edit the files in docker/compose, set port mapping for any database that you want to expose to the 'outside world' and restart the stack. Note that some of the databases included in the db3v4l, such as Microsoft SQL Server, have licensing conditions which restrict what you are legally allowed to use them for. We assume no responsibility for any abuse of such conditions. Note also that there has been no hardening or tuning done of the containers running the database - the database root account password is not even randomized... Opening them up for access from external tools might result in security-related issues

  • Q: what is the level of security offered by this tool? Can I allow untrusted users use it to run any query they want? A: this is the end goal, but at the moment there is close to zero security enforced. Please only allow trusted developers to access the platform and run queries on it

  • Q: does the platform store/log anywhere the executed SQL commands? A: no. But those might be stored in the databases log files, which are stored on disk. So it's not a good idea to copy-paste sql snippets which contain sensitive information such as passwords

  • Q: how can I free up disk space after having installed this tool and played around with it? A: check out the command ./bin/dbstack cleanup in all its forms. To completely destroy the built images and containers, you can use docker-compose down --rmi all