I don’t have that many complaints about git but I don’t like how I don’t have any idea what would happen if I were to push a git-lfs repo to an arbitrary remote with no specific git-lfs awareness
- she/her
web dracat
•
made:
internet-ti.me, @Watch, Wayback Classic, etc.
•
avatars appearing:
in 2D by nox lucent
in 3D by Zcythe
•
"If it were me, I'd have [changed] her design to make [her species] more visually clear" - some internet rando
•
I post embeds of other peoples' things at @ticky-reposts
mastodon
queer.party/@tickybsky mirror
bsky.app/profile/drac.atYou must log in to comment.
in reply to @ticky's post:
maybe it would push just the non-lfs stuff and ignore the lfs objects? I actually have the LFS objects and normal objects configured to go to two different remotes for the repo for my personal site
huh, how do you actually configure LFS remotes? I haven't been able to find any documentation about how you interact with that
No clue where to find this in the documentation. I picked up the trick from this blog post on using S3 to store LFS objects to save a buck (<C-f> .lfsconfig) https://blog.dermah.com/2020/05/26/how-to-be-stingy-git-lfs-on-your-own-s3-bucket/
Though in my case I'm using github as the normal remote, and storing LFS objects on self-hosted gitea, and I noticed the gitea didn't like when I pushed LFS objects to a totally empty repo. I had to push a commit with code in it once to kick it off, then subsequent pushes only used it for LFS objects
interesting, I think this gets me closer to what I want to achieve (a remote I can push to on my NAS which supports LFS)
I assume you have some reason for not just using gitea? I run it on my NAS as a docker container with the only issue being I have to use it over HTTPS instead of SSH. Disable self service account creation if you expose it to the public net (learned that the hard way lol)
I don't need or really want a web interface on there, I just want a simple remote to push to, it's probably light enough though I suppose
