Add Docker Context Path and Recursive Options Support #194
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.
This PR adds support for two new Docker deployment options that enhance the flexibility of container deployments with Heroku:
docker_context_path
- Allows specifying a custom build context pathdocker_find_recursive
- Enables deployment of multiple Docker containers from subdirectoriesChanges Made
🔧 Core Implementation
deploy()
function to accept and use the new parametersheroku container:push
command to include--context-path
and--recursive
flags📚 Documentation
New Features
docker_context_path
docker_context_path: "."
(if you have a monorepo, for instance)docker_find_recursive
Dockerfile.<process>
files from current and subdirectoriesDockerfile.web
,Dockerfile.worker
, etc.Usage Examples