<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Victor M.</title>
    <description>The latest articles on DEV Community by Victor M. (@victor_manzaneque).</description>
    <link>https://dev.to/victor_manzaneque</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3971493%2F4606cbfa-6d8c-4fc9-9b90-f30d138cb55d.png</url>
      <title>DEV Community: Victor M.</title>
      <link>https://dev.to/victor_manzaneque</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/victor_manzaneque"/>
    <language>en</language>
    <item>
      <title>Template Django+Docker</title>
      <dc:creator>Victor M.</dc:creator>
      <pubDate>Sat, 06 Jun 2026 16:08:22 +0000</pubDate>
      <link>https://dev.to/victor_manzaneque/template-djangodocker-1l9n</link>
      <guid>https://dev.to/victor_manzaneque/template-djangodocker-1l9n</guid>
      <description>&lt;p&gt;Hello, community! 📦&lt;/p&gt;

&lt;p&gt;Today I want to share a project that I just published on GitHub. It has completely streamlined how I structure my development setups. It is an automated template to deploy Django development environments using Docker, designed under the core principle of absolute portability.&lt;/p&gt;

&lt;p&gt;As developers, we often switch between different workstations (e.g., moving from a desktop tower to a laptop). I wanted to eliminate the friction and repetitive nature of configuring local virtual environments (venv), installing specific Python versions, or dealing with dependency version conflicts on every single machine.&lt;/p&gt;

&lt;p&gt;Here is how the project works and how I tackled the configuration dynamically.&lt;/p&gt;




&lt;h2&gt;
  
  
  🛠️ The Tech Stack
&lt;/h2&gt;

&lt;p&gt;The template comes pre-configured with a lightweight base, ready for traditional web development or API creation:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Python 3.11-slim&lt;/li&gt;
&lt;li&gt;Django 5.0.6&lt;/li&gt;
&lt;li&gt;Django REST Framework 3.15.1&lt;/li&gt;
&lt;li&gt;Docker &amp;amp; Docker Compose&lt;/li&gt;
&lt;li&gt;Windows Batch Scripting (for local automation)&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  🚀 The Workflow: True Portability
&lt;/h2&gt;

&lt;p&gt;The project is built to act as a "master mold." To prevent container naming conflicts in Docker, the usage workflow is as follows:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Create a brand-new folder on your computer with your app's name (e.g., mi_app_biblioteca).&lt;/li&gt;
&lt;li&gt;Copy the original configuration files from the template into that folder (Dockerfile, docker-compose.yml, requirements.txt, and start_project.bat).&lt;/li&gt;
&lt;li&gt;Double-click &lt;strong&gt;start_project.bat&lt;/strong&gt;.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;a href="https://github.com/victor-manzaneque/template-django-docker" rel="noopener noreferrer"&gt;https://github.com/victor-manzaneque/template-django-docker&lt;/a&gt;&lt;/p&gt;

</description>
      <category>django</category>
      <category>docker</category>
      <category>python</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
