-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lifecycle Prepare Phase #555
Comments
Hi, I would like to work on this project! Do you have any tips or starting points for a newcomer? Thanks in advance |
Hi @shatoboar - apologies for the slow reply. I am sure @jkutner will have more to add, but here are some thoughts that come to mind for now:
Let us know how that sounds. We're happy to provide any further guidance as needed. For more real-time support, you could also reach out in Slack: https://slack.buildpacks.io/ |
Hi, I am using pack-cli and buildpacks on my daily development projects. This feature is sounds very good to me. I would like to work on this issue, I will read your tips. Is there any channel on slack or should i send direct message you ? |
Is there any way to specify buildpacks like |
Hi @uqix you can currently specify buildpacks in project.toml: https://github.com/buildpacks/spec/blob/main/extensions/project-descriptor.md#buildbuildpacks which is supported by pack. With respect to the lifecycle "prepare" phase and how that might interact with project.toml - lately there has been much discussion within the project about this topic, with various competing and/or complementary RFCs. I believe @jromero has a forthcoming RFC that will try to tie various ideas together. In the meantime, here are the ones that are out there:
|
If I'm not mistaken, providing buildpacks to the lifecycle would take the form of providing an RE: project.toml Latest rendition of a proposal (still very much WIP) is here: https://hackmd.io/4LGBHOZAQ6GMOTeDf2U3_w#Platform-Configuration |
@jromero thanks, problem solved by FYI, we use this [[order]]
[[order.group]]
id = "paketo-buildpacks/nodejs"
version = "0.12.0"
[[order.group]]
id = "paketo-buildpacks/nginx"
version = "0.5.2" |
Blocking this on buildpacks/rfcs#202 |
Overview
This is a proposal for a Lifecycle
prepare
phaseGoals
Specifications
A new Lifecycle phase and associated binary should be available to Platform Implementers, and should be executed by Pack.
Milestones
Prior Art
The text was updated successfully, but these errors were encountered: