feat: automate migrations and standardize docker environment#17
Open
feat: automate migrations and standardize docker environment#17
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR introduces Docker to our development workflow. It standardizes our environment (Python 3.11, system dependencies) and automates the database setup process to eliminate "it works on my machine" issues.
Key Changes
Automated Migrations: The container now runs python manage.py migrate automatically on startup. No more manual migration steps needed after pulling new code.
Environment Parity: Everyone now runs the same Linux-based environment, matching our intended production setup.
Security & Configuration: Moved sensitive settings (Secret Key, Debug mode) to a .env file structure (check the updated README for the template).
Optimized Build: Added .dockerignore to keep images small and prevent local junk (like db.sqlite3 or venv) from leaking into the container.