Skip to content
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

Remove the Fetcher #6

Closed
arschles opened this issue Nov 23, 2015 · 1 comment · Fixed by #171
Closed

Remove the Fetcher #6

arschles opened this issue Nov 23, 2015 · 1 comment · Fixed by #171
Assignees
Labels

Comments

@arschles
Copy link
Member

The buildpack builder has a fetcher, which acts as a slug and tar specific network storage system. Its implementation is to store slugs and tars in specific locations on the local filesystem. It appears that the fetcher's goal is to be a fallback in case S3 is not configured for the install.

We're adding support for minio (see Object Storage in deis/deis#4743), which is a more general purpose object storage system that can run in the cluster (currently its implementation is also to store data on the filesystem) in v2 Alpha.

I'm proposing that we remove the fetcher and require that either S3 or Minio access is configured for builder and slugbuilder.

cc/ @smothiki

@smothiki
Copy link
Contributor

+1. I think you already have code in place which avoid need for fetcher component. Just needs to change entrypoint.sh

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants