search

xpollen8 / jazzbutcher.com

Hub for collecting/maintaining, and discussing preservation efforts of the materials shared with the world at jazzbutcher.com
http://jazzbutcher.com
2 stars 0 forks source link

Shared S3 bucket access strategy #48

Open xpollen8 opened 3 years ago

xpollen8 commented 3 years ago

In order for multiple people to contribute large media items, there needs to be a way for shared access to the S3 bucket that exists.

Idea: a simple uploader app. Challenge: enforcing proper issue tracking.

Perhaps each upload requires an Issue as a reference, and it drops into a new Incoming Bucket.

Then things simply need to be moved from Incoming -> the proper destination.

wnerini commented 3 years ago

I know it's possible to sync to an S3 bucket with GitHub server actions. But I've only just skimmed the tutorials. (been working in Azure environments lately. ) But I think that's unavailable here on github.com.

For an uploader app/page, tracking can be accomplished by requiring an issue number as part of the upload. If we wanted to get fancy, the uploader could check the validity of the issue number.

if (getHttpReturnCode('https://github.com/xpollen8/jazzbutcher.com/issues/' + issueNum) <> 200) { // tell them no }

xpollen8 commented 3 years ago

Yup. I'm working on something almost exactly as described.

I already have an uploader component in another project, just need to rip it out for this