@@ -140,7 +140,9 @@ See the section 'Alternative commands to dbstack' below for examples.
140140
141141### Maintenance
142142
143- 3 scripts are provided in the top-level ` bin ` folder to help keeping disk space usage under control
143+ The ` ./bin/dbstack cleamup ` command is provided to help keeping disk space usage under control. It can remove the
144+ log files produced by running the application, as well as the complete set of database data files.
145+
144146
145147### How does this work?
146148
@@ -151,7 +153,7 @@ Docker is used to run the app:
151153- each db instance runs in a dedicated container (except SQLite)
152154- one container runs the web interface
153155- one container runs the command-line tools which connect to the databases
154- - one container runs Adminer, a separate, self-contained db administration app, also written in php
156+ - one container runs Adminer, a separate, self-contained db administration web app, also written in php
155157
156158Docker-compose is used to orchestrate the execution of the containers, ie. start, stop and connect them.
157159
@@ -165,7 +167,7 @@ from the `dbconsole`.
165167This design has the following advantages:
166168
167169- parallel execution of queries across all database instances to reduce the total execution time
168- - it does not let the warts of php database-connectors influence the results of query execution
170+ - it does not let the warts of the php database-connectors influence the results of query execution
169171- it can easily expand to run queries on multiple database types, even those not supported by php
170172
171173On the other hand it comes with some serious drawbacks as well, notably:
0 commit comments