Answer the question
In order to leave comments, you need to log in
Whether to store images in GIT'e?
There is a "web-application", in fact - a directory. Each item in the catalog has an image. Images are not a particularly necessary detail, but they make everything look more fun and, perhaps, clearer.
There are several hundred items in the catalog, the same number of images, weighing half a megabyte each.
If the image is stored in the repository, and someone wants to clone the project for himself to edit the code, then he doesn’t need the pictures at all, and they will download for a relatively long time.
If the pictures are not stored in the git at all, then it will turn out that not all project data is in the repository, which is also not very good.
So how to be?
Answer the question
In order to leave comments, you need to log in
If the pictures are part of the project, then it’s better to store them, if it’s dynamic data, then no
So how to be?Decide whether the pictures are part of the source code or still part of external / temporary data? If a part of the source code (for example, a logo from a website layout) is to be saved, if it is just some temporary data, give it out separately to everyone who wants it.
See why you asked this question.
The problem with binaries in the git is that you can’t cut them out of there and over time the turnip becomes monstrous.
If you want to store binaries in the git, then create a separate turnip and screw it with a submodule.
normally, pictures are not stored in the repository if the pictures do not relate, for example, to the theme of the site (background, icons for the basket and buttons, etc...)
GitLFS is specifically designed to keep large files separate from the main repository.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question