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

Media asset make the repo heavy. #20

Open
pythonbrad opened this issue Jan 21, 2024 · 3 comments
Open

Media asset make the repo heavy. #20

pythonbrad opened this issue Jan 21, 2024 · 3 comments

Comments

@pythonbrad
Copy link
Member

pythonbrad commented Jan 21, 2024

Problem

The repository is little huge to download. And with the time, it will become bigger.

Possible solution

  • Move all the current media in the cloud.
  • Use link to asset (photo, image, ...) instead of push the article with his assets.
@pythonbrad pythonbrad changed the title Move media asset in the cloud. Media asset make the repo heavy. Jan 21, 2024
@monkeyK1n9
Copy link

monkeyK1n9 commented Jan 21, 2024

Possible solution:

The blogs can be pushed to another repo with the media there, so that the code is separated from the blogs and media files.
The .mdx files and media will be fetched when the user opens the blog page on the web.

(We are running away from cloud solution, but hey, let the others have a word on this).

@tericcabrel
Copy link
Contributor

Hello @monkeyK1n9, @pythonbrad 👋🏾
Let's assume we host them in the cloud. How do you see a user's writing experience when they need to add an image while writing?

@RMPR
Copy link
Collaborator

RMPR commented Jan 25, 2024

@pythonbrad my 2c, if you really care about that, you could use sparse checkout or shallow clone

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

No branches or pull requests

4 participants