playframework / playframework/playframework.com
Avoid depending on local files manually downloaded
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 44
- Forks
- 62
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 3
Description
playframework.com requires a handful of manually downloaded stuff:
- translations
- play1 modules
- generated docs
- etc...
(check README.md and the data/).
Depending on that makes it painful to rebuild the production machine or run the website on heroku or other clouds.
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 reading README.md and inspecting the data/ directory to identify the manually downloaded translations, Play 1 modules, and generated documentation. Determine how these assets are currently obtained and define a rebuild and deployment path that does not depend on local files; done means the website can be rebuilt for a production machine or Heroku without manual downloads.
Written by the indexing model from the issue text.
Assessment
- Domain
- cloud, devops
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100