This commit significantly improves the local development experience by enabling hot reloading for the Django application. This is achieved by installing the project as an editable package within the Docker services.
Key changes:
- **Hot Reloading:**
- Modified `docker-compose.yml` for `web` and `celery` services to use `uv pip install --editable . --no-deps`.
- Mounted the project root (`./`) to `/code` in `web` and `celery` services to facilitate the editable install.
- **Docker & Build Enhancements:**
- Added `uv` binary to stage-1 in the `Dockerfile` for faster package operations.
- Adjusted file permissions in `Dockerfile` during the app copy.
- Set `DEBUG=true` for the `web` service in `docker-compose.yml` for easier local debugging.
- Changed `restart` policy to `unless-stopped` for `web` and `celery` dev services.
- Added a healthcheck for the `redis` service in the dev `docker-compose.yml`.
- **Code & Script Cleanup:**
- Removed the custom `HealthCheckView` from the `home` app, as health checks are now handled by django-health-checks.
- Updated paths and commands in `scripts/entrypoint.sh`, `scripts/prebuild.sh`, and `scripts/reset-db_make-migrations_seed-data.sh` to align with the new setup and remove obsolete steps (e.g., db cache table creation; we now use redis).
|
||
|---|---|---|
| .devcontainer | ||
| .github/workflows | ||
| .vscode | ||
| scripts | ||
| seed | ||
| server | ||
| src/pkmntrade_club | ||
| .cursorrules | ||
| .dockerignore | ||
| .envrc | ||
| .gitignore | ||
| .python-version | ||
| CONTRIBUTING.md | ||
| docker-compose.yml | ||
| Dockerfile | ||
| fly.toml | ||
| LICENSE | ||
| locustfile.py | ||
| manage.py | ||
| MANIFEST.in | ||
| pyproject.toml | ||
| README.md | ||
| uv.lock | ||
PKMN Trade Club
PKMN Trade Club is a Django-powered application built to connect Pokémon TCG Pocket trading enthusiasts in a secure, scalable, and community-driven environment. This platform leverages Django’s robust features and stability, a modular project structure, and best practices to deliver a smooth trading experience.
Table of Contents
Features
- Django & Python: Built with Django 5.1 and Python 3.12.
- Modular Architecture: Separate Django apps for trades, accounts, cards, and more.
- User Authentication: Comprehensive authentication powered by Django Allauth.
- Responsive UI: Custom theming with Tailwind CSS, DaisyUI, and AlpineJS.
- Production-Ready: Docker and PostgreSQL configuration for scalable deployments.
- Development Tools: Built-in support for migrations, testing, and seeding initial data.
- Security & Performance: Carefully configured for deployment with production best practices.
Installation
Local Development
-
Clone the repository:
git clone https://git.badblocks.dev/badbl0cks/pkmntrade.club.git cd pkmntrade.club -
Install dependencies via uv:
uv pip install -r requirements.txt -
Configure environment variables:
Copy the example environment file and update credentials as needed:
cp .env.example .env -
Apply migrations and seed initial data:
python manage.py migrate python manage.py createsuperuser python manage.py createcachetable django_cache -
Start the development server:
uv run manage.py runserverVisit http://127.0.0.1:8000 in your browser.
Docker Deployment
-
Build and run containers:
docker-compose up -d --build -
Run migrations and create a superuser inside the container:
docker-compose exec web python manage.py migrate docker-compose exec web python manage.py createsuperuser docker-compose exec web python manage.py createcachetable django_cache -
Access the site:
Configuration
-
Environment Variables:
Manage your local vs. production settings using.envand.env.production. Update these to match your database credentials, secret keys, and other configurations. -
Django Settings:
Production settings are indjango_project/settings.py. -
Database Settings:
Example configuration for PostgreSQL:DATABASES = { 'default': { 'ENGINE': 'django.db.backends.postgresql', 'NAME': 'postgres', 'USER': 'postgres', 'PASSWORD': 'postgres', 'HOST': 'db', # as defined in docker-compose.yml 'PORT': 5432, } }
Database
The platform uses PostgreSQL as its primary database in production. For local development, you may use SQLite or configure PostgreSQL by updating your settings and environment variables as needed.
Running Tests
Run Django’s testing suite with:
python manage.py test
Deployment
For production deployments consider these additional steps:
- Production Server: Use a web server like Gunicorn.
- Static Files: Serve static files using Django’s WhiteNoise (or via a CDN).
- Fly.io Configuration: A
fly.tomlfile is provided if you wish to deploy on Fly.io. - Deployment Scripts: Use
deploy.shfor automated deployment tasks. - Security & Email: Update
DEFAULT_FROM_EMAIL,ALLOWED_HOSTS, and other security settings indjango_project/settings.py.
Contributing
Contributions, feature requests, and issues are welcome! Please refer to CONTRIBUTING.md for details on how to contribute to PKMN Trade Club.
License
This project is licensed under the MIT License. See LICENSE for more information.