nusmodifications / nusmodifications/nusmods
Make testing the export service locally less painful
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 689
- Forks
- 364
- Avg merge
- 7h 5m
- Merged PRs (30d)
- 14
Description
Right now, it's pretty painful to set up the export service locally for testing. There is a docker-compose config but I suspect it hasn't been tested in a while and might not work correctly anymore. We should look into making this process more convenient.
Contributor guide
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 inspecting the repository's docker-compose configuration and the export service setup. Check whether the current local testing path still works and identify the steps that make it painful. Done means the export service can be set up locally for testing through a reliable, convenient process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, javascript
- Domain
- backend, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100