Until we can implement proper multi-buildpack support, injecting the nodejs buildpack before the primary application language buildpack (but after the apt buildpack, if there is one) would enable applications with statically generated frontend assets at buildtime. This could possibly be generalized to injecting any of the builder-supported buildpacks.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Stalled | LucasWerkmeister | T320140 Migrate wd-shex-infer from Toolforge GridEngine to Toolforge Kubernetes | |||
| Resolved | matmarex | T319707 Migrate dtcheck from Toolforge GridEngine to Toolforge Kubernetes | |||
| Open | None | T320062 Migrate steve-adder from Toolforge GridEngine to Toolforge Kubernetes | |||
| Open | None | T320011 Migrate rfa-voting-history from Toolforge GridEngine to Toolforge Kubernetes | |||
| Open | dcaro | T194332 [Epic] Make Toolforge a proper platform as a service with push-to-deploy and build packs | |||
| Open | Feature | None | T305780 toolforge-jobs – wikihistory needs a container with both php7 and mono | ||
| In Progress | Slst2020 | T325799 [tbs] User story - I can use multiple language stacks for my application | |||
| In Progress | Slst2020 | T346635 [tbs][builder] Inject nodejs buildpack |