@@ -140,7 +140,9 @@ See the section 'Alternative commands to dbstack' below for examples.
140
140
141
141
### Maintenance
142
142
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
+
144
146
145
147
### How does this work?
146
148
@@ -151,7 +153,7 @@ Docker is used to run the app:
151
153
- each db instance runs in a dedicated container (except SQLite)
152
154
- one container runs the web interface
153
155
- 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
155
157
156
158
Docker-compose is used to orchestrate the execution of the containers, ie. start, stop and connect them.
157
159
@@ -165,7 +167,7 @@ from the `dbconsole`.
165
167
This design has the following advantages:
166
168
167
169
- 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
169
171
- it can easily expand to run queries on multiple database types, even those not supported by php
170
172
171
173
On the other hand it comes with some serious drawbacks as well, notably:
0 commit comments