Quickstart¶
This section takes you from a clean machine to a running Midsummer V2 instance
at {{ dev_url }}, then shows you where things live once it’s up.
- Local development setup
- 1. Prerequisites
- 2. Get the code
- 3. Configure environment
- 4. Set up the Python backend
- 5. Install frontend dependencies
- 6. Start support services (PostgreSQL + MinIO)
- 7. Initialize the database
- 8. Build the frontend into Django static files
- 9. Run the dev server
- Verification checklist
- Day-to-day workflow
- Common tasks
- Troubleshooting
- Port reference
- First steps after it’s running
The one-command path¶
If you just want a working instance fast and don’t care about understanding the steps yet, the repository ships convenience scripts:
./dev-bootstrap-start.sh # wipe + rebuild volumes, import a simulated event
./dev-launch.sh # bring up Postgres + MinIO, build UI, start server
URL:
{{ dev_url }}User:
{{ dev_user }}Password:
{{ dev_pass }}
The bootstrap path wipes the local database/MinIO volumes. For a clean interactive setup instead, use the full Local development setup.
Two ways to read this section¶
Local development setup — the canonical, step-by-step runbook (prerequisites → configure → migrate → build → run → verify), with a troubleshooting section and a port reference.
First steps after it’s running — once the server is up, where the code lives, how to make a change, and the build/test gates.
What you’re actually running¶
In local dev you run the Django backend natively (in .venv) while
PostgreSQL and MinIO (S3-compatible storage) run in Docker, and the
Angular frontends are built into Django static files.
Linux/macOS only. Windows is not supported (see the project
README.md).
Port |
Service |
|---|---|
|
Midsummer app (Hypercorn ASGI) |
|
PostgreSQL |
|
MinIO S3 API |
|
MinIO web console |
|
Redis (Celery broker — run your own) |