-
Notifications
You must be signed in to change notification settings - Fork 50
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
Save multimedia content to backup storage #23
Comments
Is this in reference to something like an s3 bucket for website assets? |
I believe it is regarding the podcast files (mainly mp3, but there are other formats as well). As for the destination goal? s3 or something else - I don't know. |
oh sorry all, this was added early in the project as a placeholder. Updating the initial comment w more details... |
@kbondarev i want to put everything in a minio bucket in a structured manner. Minio is self hosted S3, i can hit you up with write access keys :D |
@StefanS-O Oh cool! I wonder whether using Linode's S3 Object Storage (Linode - because I assume that's where the site would be hosted) might have some advantages over a self-hosted solution, like CDN capabilities and less things to manage? Do @ChrisLAS or @noblepayne have any plans or thoughts on this? |
No problem, I was just looking at the 1.0 milestone issues and saw this in there with no comment so I was curious 😁 |
Also, I know I'm not part of the JB crew, but I do think the less moving parts the JB crew has to maintain is better (at least initially 🙃). Since they already use the Linode storage for things (IIRC nextcloud & peertube) it's probably easy to add another bucket instead of having to maintain another self-hosted service (sounds like matrix by itself keeps them busier than they'd like 😅). But ya, whatever the JB team feels comfortable with 🙂 (just tossing in my 2 cents) |
I moved this to 2.0 it is not important for launch. |
A task to save all JB media related to shows, present and back-catalogue, to a single JB-controlled storage as the source-of-truth from this point forward.
Currently files are dispersed on various services, some missing, some on archive.org (#22) ...
Basically anything that's referred to by the current WP site that we don't want to loose access to before it vanishes.
Seeing the current WP as a sort of index of third-party media items for the last 10 years.. would be nice to capture as much of that as we can before it's too late.
Thus, a task to setup some cloud storage (decision on where, and which TBD) for use as the central repository for all media from JB that's being served to this website.
related to #22
The text was updated successfully, but these errors were encountered: