Feature Aptfile Dependencies #1
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation / Background
This PR introduces a new DevContainer feature, Aptfile Dependencies, that simplifies managing apt package installations in development environments. Inspired by [heroku-buildpack-apt](https://github.com/heroku/heroku-buildpack-apt), it allows developers to specify system dependencies in an
Aptfile.dev
file, automating their installation during container setup.This change is required to streamline and standardize the process of handling apt dependencies in DevContainers, reducing manual configuration and potential errors.
Example
Aptfile.dev
usage:Example configuration in
devcontainer.json
:Development Checklist