Javier Romero

It's all dependant on the application and/or buildpacks configuration. For example, here's some literature for: - Paketo Buildpacks: [Web Servers](https://paketo.io/docs/howto/web-servers/#port) - Heroku: [Java Applications](https://devcenter.heroku.com/articles/setting-the-http-port-for-java-applications)

This is a good idea. Although given that this isn't a defined contract in the [spec](https://github.com/buildpacks/spec), I think the best we can do for the time being would be to...

Confirm that this occurring along with other undefined indexed due to lazy setup mysql tables.

@samj1912 as we discussed, this RFC requires a few set of changes to align with the latest agreed upon strategy. Please let me know when it's updated and I'll review/start...

> I updated the rfc with the sub-directory proposal instead of the prefix one as discussed in the last WG meeting. This makes it sound like the sub-directory structure would...

Really like the directory restructure. The term `buildpack-workspace` is a bit of a mouthful so I may bikeshed on it a bit but it totally makes sense IMO.

Based on further conversations of additional "operations" such as prepare (this RFC), [publish](https://github.com/buildpacks/rfcs/pull/203), and [cosign](https://github.com/buildpacks/rfcs/pull/195) we are considering moving forward with an "implement first and standardize later" strategy. This approach...

Update: a new repository with this work has been started here: https://github.com/jromero/cnb-prepare

Update: a new repository with this work has been started here: https://github.com/jromero/cnb-prepare

Blocked by release of [project descriptor 0.2](https://github.com/buildpacks/spec/milestone/16)