loopbackio / loopbackio/loopback-next

docs: add deployment guide for Cloud Native Buildpacks.

Open
#5,190 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Docs feature
Dominant language
TypeScript
Stars
5.1k
Forks
1.1k
Avg merge
2d 21h
Merged PRs (30d)
27

Description

Currently, we have documentation on how to deploy to Cloud Foundry (CF) using CF Buildpacks.

However, the Cloud Foundry Foundation (CFF) has been shifting its focus to adopting the new [Cloud Native Buildpacks](http://buildpacks.io/) (also called "buildpacks v3" or "CNB") standard which is an open standard that adds the concepts of layers to make it more modular than typical Dockerfiles. It also can be deployed to other infrastructures that accept OCI-compliant images such as Kubernetes.

Furthermore, the CFF has recently launched [Paketo Buildpacks](https://paketo.io/) as their lineup of CNB builders.

## Suggestion

Add a guide on how to deploy a LoopBack application using Paketo Buildpacks.

CF Buildpacks (also known as "buildpacks v2") will continue to be supported for the foreseeable future. Hence, the current CF deployment docs should not be succeeded or removed.

## Use Cases

This can be useful for users who want to quickly deploy applications using the CNCF Buildpacks spec.

## Examples

TBD

## Acceptance criteria

TBD - will be filled by the team.

## Further reading

Paketo Buildpacks FAQ - https://docs.google.com/document/d/1UZCF1npw1Pfv-9VPGM7mdDpe2Q8fPdaAtfMXH2AWO0c/view

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the existing Cloud Foundry deployment documentation, then review the Cloud Native Buildpacks and Paketo links in the issue. Produce a guide for deploying a LoopBack application with Paketo Buildpacks while retaining the current CF Buildpacks guidance; the examples and acceptance criteria still need to be defined by the team.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes, nodejs, typescript
Domain
cloud, devops, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.