cloudfoundry / cloudfoundry/stratos
Make the effects of scaling a `cf push` deployment clearer
Open
Nobody has claimed this yet.
documentation
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 137
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 77
Description
- sqlite vs persistent storage
- 'db' per instance in sqlite
- push for binding persistent storage service when using multiple instances
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
No file, test, or entry point is named. Start by locating the documentation or deployment guidance for scaling a cf push deployment, then compare its treatment of SQLite, per-instance databases, and persistent storage services. Done means the guidance clearly explains these effects when increasing instance count.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sqlite
- Domain
- cloud, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100