4/2/2023 0 Comments Git annex vm applianceand have the final images generated by your build system. What you could do though, is only store "source" images: SVGs, LaTeX macros, etc. In my opinion, you shouldn't worry about it - granted you don't store GBs of those. And if they get removed over time, it's only your server that suffers a bit from storing the history, but clients won't see a thing. And if the images won't be changed that often, then where's the problem? You won't get a big fat delta. Worst case, if you have tons, store them somewhere else or use externals or an extension for binary support. Storing binaries is considered bad practice, yes, but I never worried too much about images. I am afraid at $100/terabyte, that excuse is wearing a bit thin. Same applies to any and all binary files that fit the above criteria. I have seen an entire project's original artwork go "poof" when the graphics designer's MacBook hard drive died, all because someone, with infinite wisdom, decided that "binaries don't belong in rev control", and graphics designers (at least this one) don't tend to be good with backups. Why introduce "copy and rename" version control from the dark ages? Put them in your revision control, if they never change, the space penalty is the same as a backup, and they are where you need them.Ĭan they be edited to change the appearance of the software, accidentally or intentionally? Yes - then they MUST be revision controlled somehow, why use another way when you have a perfect solution already. If they are original, they need backing up. Are your images original work or can they be recovered (guaranteed?) from elsewhere? Are they needed to ship a software unit built from source?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |