<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DDEV on The Russian Lullaby</title><link>https://www.therussianlullaby.dev/tags/ddev/</link><description>Recent content in DDEV on The Russian Lullaby</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Mon, 30 Dec 2019 00:00:00 +0000</lastBuildDate><atom:link href="https://www.therussianlullaby.dev/tags/ddev/index.xml" rel="self" type="application/rss+xml"/><item><title>Books/ Local Web development with DDEV</title><link>https://www.therussianlullaby.dev/blog/books-local-web-development-with-ddev-explained/</link><pubDate>Mon, 30 Dec 2019 00:00:00 +0000</pubDate><guid>https://www.therussianlullaby.dev/blog/books-local-web-development-with-ddev-explained/</guid><description>&lt;p>Lately, I&amp;rsquo;m interested in improving the tools of the project&amp;rsquo;s stack, thanks to the advice of a friend I approached DDEV. I already knew Docker and everything related to its ecosystem (Docker, Docker-Compose, Docker Engine, Docker Swarm&amp;hellip;) although it is true that not in a very advanced way in general, only at the level of the daily needs or small test games&amp;hellip;so I recently acquired the book &amp;ldquo;Local web development with DDEV explained&amp;rdquo; written by Mike Anello and I&amp;rsquo;d like to share my thoughts on that here.
So, Do you develop projects based on Drupal? do …&lt;/p></description></item><item><title>Docker, Docker-Compose and DDEV - Cheatsheet</title><link>https://www.therussianlullaby.dev/blog/docker-docker-compose-and-ddev-cheatsheet/</link><pubDate>Sun, 09 Jun 2019 00:00:00 +0000</pubDate><guid>https://www.therussianlullaby.dev/blog/docker-docker-compose-and-ddev-cheatsheet/</guid><description>&lt;p>As I mentioned in a previous month&amp;rsquo;s article, I&amp;rsquo;m still using / playing / practicing with DDEV to build development environments in an agile way. And the truth is that the experience couldn&amp;rsquo;t be more nicer.
We know that for some years, working with Docker Engine has become a MUST. From our ability to define specifications(Dockerfiles), configure autobuilds in the cloud to generate images from our repositories(Dockerhub), run images and containers(Docker), connect containers and relate them(Docker-Composer) or deploy container networks( Docker Swarm) &amp;hellip; on this depends …&lt;/p></description></item><item><title>Creating development environments for Drupal with DDEV</title><link>https://www.therussianlullaby.dev/blog/creating-development-environments-for-drupal-with-ddev/</link><pubDate>Sat, 18 May 2019 00:00:00 +0000</pubDate><guid>https://www.therussianlullaby.dev/blog/creating-development-environments-for-drupal-with-ddev/</guid><description>&lt;p>Well, at this moment we cannot deny that containerization is a basic pillar of our project work: the ability to compartmentalize the technological stack of each project is a fundamental resource (and be wary of those who do not practice it). But the point is that I have a new toy to play with it. Let me explain: I always (or almost always) had worked on Drupal projects with the same stack of versions, so I only had one environment set up. Then, I started to have different versions (Drupal 6.x, Drupal 7 &amp;hellip; 8) at the same time for diverse projects and then I started playing with Docker. …&lt;/p></description></item></channel></rss>