drupal-container VS lando

- name: Drupal git project test install become: yes hosts: all tasks:     - name: Ensure directory exists file: group: root owner: root path: "{{ service_directory.drupal_directory }}" state: directory     - name: Clone the sample project become: yes ansible.builtin.git: repo: https://github.com/geerlingguy/drupal-container.git dest: " {{ service_directory.drupal_directory }} " clone: yes recursive: yes

Still remember https://lando.dev/ ?

I see folks recommending Docker and DDev, which are fine options from my experience, but I also wanted to mention Lando. The team I'm on recently adopted it as part of moving our WordPress network to something deployable, and it has gone pretty smoothly.

Learn about lando.dev (docker container recipes) and how you can run pantheon configured drupal apps on your workstation with it.

Here at Jüssi, we use Docker and Lando as a solution for local development environments and manage Drupal's configurations via Composer. Therefore, we use the 'lando' command as a prefix in the commands below.

Lando (which runs on Docker), which runs on Windows 10 (work) or 11 (home) on WSL2.

https://lando.dev/ — Local environment with recipes and docker.

I'm surprised nobody has mentioned Lando. It uses docker/docker compose under the hood, but adds a further layer of abstraction to make it even easier. Comes with base recipes out of the box for Drupal/WordPress/etc.

Lando, https://lando.dev, has support for pull/push to some hosts.

The most popular is https://ddev.com. Lots of people also use https://lando.dev. I'm old-school, so I tend to use https://www.mamp.info/en/mamp/mac/

I spend most of my day writing PHP, HTML, CSS, and JS running the apps I build and support in Docker via Lando (https://lando.dev) (I mainly build and support Drupal web applications)