-
-
Notifications
You must be signed in to change notification settings - Fork 580
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ddev v1.19.0 test plan - community help requested! #3645
Comments
Just started to test Magento 2.4. My test project started without any issues and without any modification. |
|
On my Arch Linux (amd64) machine. ✅ ddev get drud/ddev-beanstalkd Redis service -> "No releases found for ddev-redis" |
Tested on MacOS 10.13.6, Docker 2.4.0.0. and Mutagen activated.
the if statement shoulnd't be shown imho
the docker volume rm line should also be hidden imho. and when restarting the project after
so as a user you have no idea if the dl is stalled or not and if things still advance correctly. after installing and downloading all available images i've applied ddev get for memcached in another project and the image hasn't downloaded a second time. so no surprises and everything behaves as expected. Postgres 9 minimum requirement for drupal 9 is postgres 10 so i stopped at that point Postgres 10
and with
i think keep things consistent would be the better choice either make all app starts verbose or let all behave like
that way it reads the command
switched then to
performed a |
@rpkoller thanks so much for your testing! It's going to be a little too messy to discuss these in the issue here, so could we discuss in Discord or slack (Already created thread in discord). Some of the things are misunderstandings (the one about ddev import-db not finding file). Others like not becoming healthy definitely need discussion. I imagine they have to do with the timeout value and your ancient machine, but definitely need discussion. But this issue will die a horrible death if we chase those here. Better to confirm in another venue and open separate issues. |
Testing in Gitpod (empty workspace-full environment, Docker version 20.10.12, build e91ed57, Ubuntu 20.04.4 LTS)
|
Not sure how this new option was finally implemented. I use a custom implementation for a longer time, where I just set the environment variable
which on the other hand then again reads
|
@h1nds1ght I hope you'll test it and report your findings. If you don't like it a new issue or a discussion in Discord would be great. What it does is the regular install.sh for nvm, but the primary system node version is set with |
I tested it. For me it works perfect within its limits. I can change to node versions 12, 14, 16 and 17 and This is much better than before, of course, but there also might be people still using deprecated versions like 8. You might say, they can use the new But what seems new is that my approach doesn't work anymore with v1.19, I always get node version 12, because my nvm at $HOME is superseded by an nvm at |
Thanks - in that case you haven't tried nvm, which allows anything. Please try out |
I'm working on
The nodejs_version is implemented at image build time, before nvm can even exist. There's probably some way to do what you ask, but we'll see how this goes for now. I suspect that even just the config.yaml option will work great for lots of people, and then nvm users will probably be happy too. Also see
|
Rerun of most of the steps with RC3 - Tested on MacOS 10.13.6, Docker 2.4.0.0. and Mutagen activated.
seems the |
Calling this one good. Thanks to all of you for testing - it made a huge difference. Followups are welcome, of course. If you thing something should still be addressed, feel free to comment here or open a new issue. |
It's testing time again here in the DDEV-Local factory. We love community help with every item that is interesting or relevant to you, and just using the release candidates is hugely helpful, because you may stumble across something in your regular workflow. Please use ddev v1.19.0-rc2 or later for your testing (or
brew install --HEAD ddev
).I don't think in general you'll have trouble using this in your daily workflow, so would love you do do that. You can switch back and forth , see How can I install a specific version of DDEV in the FAQ.
If you find a bug that you're pretty sure is a bug, then [just open an issue for it](https://github.com/drud/ddev/issues/new?assignees=&labels=&template=Bug_report.md&title=).
To give feedback or ask questions, please just reply on this issue or discuss in [discord](https://discord.gg/hCZFfAMc5k) or another other support channel.
I am maintaining the provisional release notes for v1.19.0 and would love any comments on those.
ddev debug dockercheck
ddev debug test
$PATH change inside web container using homeadditions/.bashrc.d/path.sh (docs)
ddev exec
and custom web commands can behave much better in combination with quotes, see 'ddev composer',ddev exec
, and shell commands likeddev drush
do not support quotes, breaking lots of things #2547ddev get --list
andddev get --list --all
ddev get
now provides access to tested and supported services/recipes (see docs). Try each official recipe:ddev get --list
ddev get drud/ddev-beanstalkd
ddev get drud/ddev-memcached
ddev get drud/ddev-redis
ddev get drud/ddev-drupal9-solr
ddev service enable
andddev service disable
swapdocker-compose.<service>.yaml
in and out of the .ddev directory. Test out.Database configuration changes from
mariadb_version
andmysql_version
todatabase: mariadb:10.5
anddatabase: mysql:5.7
anddatabase: postgres: 14
.ddev config --database=postgres:13
for examplemariadb_version
andmysql_version
should still work.Postgresql support: Use database type
postgres:9
throughpostgres:14
and make sure it works where needed. (Snapshots not allowed on postgres:9)ddev export-db
ddev import-db
ddev snapshot
ddev snapshot restore
macOS: Use ddev with Colima
windows WSL2: Use ddev with inside-wsl2 installation of docker and with Docker Desktop turned off. (docs
Test with remote docker instance (docs). You may want to try this with a VM running docker.
Bare in-container hostnames: You can (once again) use in-container hostnames like
db
orsolr
without having to use fully-qualified names likeddev-<project>-db
. Verify that ddev web container has no ambiguity even withoutlinks
. See testing instructions in Use simple container name as hostname inside docker network (use "db" instead of "ddev-<project>-db") #3403Test improved WordPress setup per Fixes DDev WordPress Config Files for Override & Coding Standards, fixes #2795 #3468. See manual testing instructions there.
Gzipped database snapshots:
ddev start
now tests available disk space against an absolute value (5GB) rather than a percentage. Test to make sure that it does flag low values. This can be done with artificially using space or by altering the value in nodeps/values.go (Also see The absolute available space value was wrong for checking docker disk space #3646)Verify that graphicsmagick is installed in web container
Fresh Drupal 10 install should get PHP Version 8.1
Fresh Laravel install should get PHP Version 8.0
ddev tableplus
should work for both mysql/mariadb and postgres projectsnodejs and nvm support
ddev nvm
to get any nodejs version.Gitpod users should be able to use Xdebug, Remove special handling for gitpod getting host.docker.internal #3597
ddev delete
should delete any volume named in anydocker-compose.*.yaml
when mutagen_enabled, ddev now mounts upload_dir into container using regular docker bind-mount.
Verify that segment/amplitude reporting is working adequately.
A new ddev project should be able to start up even if there’s no internet (assuming images have been downloaded already)
ddev debug download-images
should download default images (maybe more???) and also get docker-compose and mutagen.New
ddev php
commandNew
ddev debug clean
command (WIP, not in v1.19.0-rc1)Ability to use
ddev config global --no-bind-mounts
to not use docker bind mounts at all (for remote machines, where $DOCKER_HOST is used, etc.) Test with a remote machine.docker-compose v1: Use
ddev config global --required-docker-compose-version=v1.29.2
and verify normal usage.Casual Webhosting: Verify that casual webhosting feature is working OK.
The text was updated successfully, but these errors were encountered: