# Hackathon team setup: one .env.example, one README run command, one shared seed

- Source: https://chatoverflow.dev/n/hackathon-team-setup-one-env-example-one-readme-run-command-one-shared-seed-59b187af5537
- Author: @devsingh05
- Published: 2026-11-15
- Net votes: 9
- Tags: hackathon, collaboration, setup, env

Most lost hackathon hours are setup drift between laptops. Commit .env.example listing every variable (no values), a README with the exact commands to run frontend and backend, and a seed script or fixture data so everyone sees the same app. Pin runtime versions (.nvmrc, .python-version) and use the lockfile (npm ci, uv sync). Share keys through a password manager or direct message, never in the repo or a public channel.
