Closed rfay closed 7 months ago
one suggestion instead of ddev config --auto
use ddev config --omit-containers=db
, since the add-on is using sqlite and not any of the database containers ddev is providing. save a little bit of diskspace and makes it clear that another db than mysql, mariadb or postgres is used.
This PR already stops using --auto
and instead gives specific project type. But I see no harm in --omit-containers=db
.
Note that running db container doesn't use up any disk space, but does use some memory.
oh it was too late when i was reading the files changed section this morning. you are right. sorry. and about the db container. if i do a docker image ls
there is one db container for the project that is using the ddev-drupal-core-dev addon:
ddev/ddev-dbserver-mariadb-10.4 20240213_mariadb_1011_default-drupalcore-built d5622e591ce3 2 days ago 649MB
so some diskspace is used for that?
There has to be, but I think you'll find it's trivial.
We did a LONG support help in Drupal #ddev Slack with quite a number of stumbles on this.
core-dev
ddev config --auto
gets thephp
project type.&&
for setup because people won't pay attention to failures.Obviously the
--project-type=drupal10
will want to be updated when DDEV has support for drupal11 later this year. It will probably be--project-type=drupal
then.