loopbackio / loopbackio/loopback-next
Easy deploy to Cloud/Production Epic
Open
Nobody has claimed this yet.
CloudNative
epic
feature
major
- Dominant language
- TypeScript
- Stars
- 5.1k
- Forks
- 1.1k
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 27
Description
We should make it easy to deploy LoopBack4 applications to most common production types:
- IBM Cloud & API Connect
- Twelve-factor platforms (e.g. Heroku), where configuration is read from environment variables (e.g. PORT, database connection strings, etc.)
- Docker and Kubernetes
- http://istio.io/
- Enable LB apps to be Cloud Native
Re-posting from https://github.com/strongloop/loopback-next/issues/1054:
- How do I modify behavior of my LoopBack4 application in production, e.g. modify error responses to not leak any sensitive data?
- How do I configure database connection strings, access credentials, port number to listen on, etc. for my LoopBack4 application?
- How can I secure my application? (This overlaps with the existing epic of Authentication/authorization/security.)
- How do I monitor behavior of my LoopBack application in production, what useful insights can I get on top of usual low-level Node.js metrics?
- How can I upgrade my applications with zero downtime? Is there anything special needed to enable blue/green deployments?
- Where can I find logs from my app? How can I produce my own log entries from my custom code (e.g. controller methods)?
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 reviewing the production deployment goals listed in this issue and the linked prior issue. Break the epic into a concrete deployment target or question, such as environment-based configuration, Docker/Kubernetes, logging, monitoring, or zero-downtime upgrades. Done should be a separately scoped change with a clear implementation and verification path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes, node.js
- Domain
- backend, cloud, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100