Im hard considering moving to fossil just because it has a lot of nice facilities for tracking things not related to source version control, but things that are still important. bug trackers, wiki, and technotes are all very tempting
Timeline
Post
Remote status
Context
8
@theorytoe I thought about it but the implications of having your whole project in a sql database terrifies me
@RustyCrab @theorytoe nah, sqlite is rock solid. Plus if you're rocking everything forked from gogs, you're probably putting everything (sans code) in sqlite anyway.
@pwm @theorytoe bitrot and sqlite do not mix
how does git handle things if you flip a couple random bits in it's .git dir? probably just as well as if you did it in a sqlite.
Plus you probably aren't going to keep your entire project on an abused one of these (I will likely not use fossil and just continue using git because I like goysvm)
Plus you probably aren't going to keep your entire project on an abused one of these (I will likely not use fossil and just continue using git because I like goysvm)
@tyler @theorytoe @pwm if you flip bits on a git LFS object (the vast majority of storage) it will result in a recoverable smudge error but your repo is still fine. Less sure about core objects or pak files
is coming for us all
Replies
6
@RustyCrab @theorytoe @tyler I also did do some shenanigans to reduce the amount of transfer that happens but
while you sleep unsuspectingly
@RustyCrab @theorytoe @tyler If you transfer less than some multiple of what is stored, it's free. They had like 100 gigs of media when I put it up there and we use way less than that a month.
