Ainsofs Blog: Technology insights from the Pacific Islands

I've started experimenting with DDEV for local development environments. It provides simple commands to quickly get you up and running compared to docker4drupal . However docker4drupal has the upper-hand when you want to restore databases into your dev environment. Its easier and faster compared to drush sqlc or DDEV commands. To enable this feature on docker4drupal, uncomment these lines in the mariadb container. Next create a folder called mariadb-init and drop your db in there then start up your container. It will pickup any files with *.sql or *.sql.gz If your container is already running you'll need to restart it. I find that its easier to destroy it and start again. docker compose stop mariadb && docker compose rm -f mariadb && docker compose up -d Tip: Ive made this easier by adding an alias called dbdb to run the above. Now if I need to debug an issue using a snapshot of production data, I can load it into the mariadb-init folder and run dbdb to start...

  Some cool tools from todays pod casting on exploring code ideas without having to build up the whole stack. You can listen to the full pod cast here .  Try and combine different JS code snippets - https://www.val.town/   Writing notes with embedded JS code snippets that run on demand - https://observablehq.com/   Svelte play ground - https://svelte.dev/repl/hello-world?version=4.2.15   Lite Dbs - https://orm.drizzle.team/docs/get-started-sqlite   Updated 10 June 2024 Since then I've also discovered how you can quickly run drupal in the cloud to play around and explore some ideas. Spin up a drupal instance using Gitpod Spin it up with DDEV installed