Should host images be tracked in git #234
Labels
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: HPR/hpr_generator#234
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Should we be tracking images in git ?
https://repo.anhonesthost.net/HPR/hpr_generator/src/branch/main/public_html/images/hosts
Yes, I have been thinking of adding a "resources" folder to the templates folder. This would be for static content like the images and css which would go into git, and then copied over to public_html folder when stuff is generated. I would like to keep the public_html from the hpr_generator repository.
We could then have a separate repository of all the static files in the public_html folder. This would be the repository someone could just clone to host the site and then pull to keep updated.
My question was more about storing binary blobs in git was frowned upon in general. Religious wars et al.
@archer72 Mentioned git-lfs in hpr4172
An open source Git extension for versioning large files
Git Large File Storage (LFS) replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server like GitHub.com or GitHub Enterprise.