Skip to content
This repository has been archived by the owner on Jun 20, 2018. It is now read-only.

Better organization for S3 buckets #65

Closed
bgentry opened this issue Sep 19, 2013 · 3 comments · Fixed by #67
Closed

Better organization for S3 buckets #65

bgentry opened this issue Sep 19, 2013 · 3 comments · Fixed by #67

Comments

@bgentry
Copy link
Collaborator

bgentry commented Sep 19, 2013

I'm thinking we could use a cleaner hierarchy for builds and diffs in the S3 buckets. Currently, everything gets thrown directly into the top level of the bucket. Instead, I'd like to prefix to get some better organization. Examples:

# dist bucket: (/version/platform.gz)
/v20130919/darwin-amd64.gz
/v20130919/linux-arm.gz
/v20130919/windows-amd64.gz

# patch bucket: ( /from/to/platform.gz )
/v20130917/v20130918/darwin-amd64.gz
/v20130917/v20130918/linux-arm.gz
/v20130917/v20130919/darwin-amd64.gz
/v20130917/v20130919/linux-arm.gz

I think this will make it easier to clean out old bins and patches, and also makes it easier to see which patches have been generated.

@kr
Copy link
Owner

kr commented Sep 20, 2013

Do you suggest leaving out the name field?
(Currently always hk.) It's there in case we
also want to distribute plugins.

@bgentry
Copy link
Collaborator Author

bgentry commented Sep 20, 2013

No, sorry, the highest level prefix should be the name. So /hk/20130919/darwin-amd64.gz for example

On Thursday, September 19, 2013 at 5:41 PM, Keith Rarick wrote:

Do you suggest leaving out the name field?
(Currently always hk.) It's there in case we
also want to distribute plugins.


Reply to this email directly or view it on GitHub (#65 (comment)).

@kr
Copy link
Owner

kr commented Sep 20, 2013

Sounds good to me.

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

Successfully merging a pull request may close this issue.

2 participants