Seed data on first clone
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 16
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Do something please. Similar to https://github.com/PEC-CSS/acm-website-backend/issues/67 but this one for frontend docker compose containers
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the related backend issue 67 and the frontend Docker Compose configuration. Determine what seed data the frontend containers require on a first clone, then verify that a fresh setup creates that data automatically.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, typescript
- Domain
- devops, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100