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

Pick and deploy a filesharing solution to avoid media bloat in the repo #519

Open
YuriSizov opened this issue Jan 16, 2023 · 0 comments
Open
Labels
enhancement topic:backend Issues and PRs related to the backend and the build system

Comments

@YuriSizov
Copy link
Contributor

We've got rid of the CMS, but that makes handling of the media files a bit clunky. You have to PR them together with the articles, which is not bad, but that also means that the repo has to keep hundreds of megabyte of images and videos in its history.

We've discussed this a bit with @coppolaemilio and we should probably look into a lightweight solution for filesharing and file hosting, that we can self-host on TuxFamily. It should come with access management, so it can only be used by maintainers, but its role should be simple: drop a file, get a URL back. It would be also nice if we could customize the upload paths so the files are hosted in the download repository on TF, as recommended by TF themselves for static content like that.

@YuriSizov YuriSizov added enhancement topic:backend Issues and PRs related to the backend and the build system labels Jan 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement topic:backend Issues and PRs related to the backend and the build system
Projects
None yet
Development

No branches or pull requests

1 participant