Wolf Noble

technically false… because the .git directory/history remains in the repo, and that’s >half the problem. extracting the core to a new repo would be the least painful way to address...

that would require @nunocoracao to maintain two copies of the same codebase… more toil, greater chance for divergence. what feels least bullshitty to me is having a core repo that...

implementation details :) lots of ways to accomplish it… each has its own bag of bullshit… i don’t wanna be too prescriptive of the how… just wanting to amplify the...

@nunocoracao if you wanna take a look at what I'm doing async: I mirror this repo: https://gitlab.wolfspyre.io/mirrored_repos/hugo_related/nunocoracao/blowfish The scripts here rip the history around quite a bit... might be useful...

I'm not gonna assert this is perfect :) it's kludgey... and a bit brittle... but it works for the moment.... an it might be helpful as exploratory POC. Will reach...

@nunocoracao it’s possible for sure, but every path comes with caveats… when you rewrite history, it invalidates others’ versions of it.. :) so it’s something that needs to be done...

something to keep in mind.... git history keeps EVERYTHING that EVER was in the repo.... every time you convert an asset, you're increasing the repo size by that much... This...

@ragibson my ci already is doing so, (plus I haz local mirror of repo so its less of an issue (FOR ME) but that's beside the point of curbing the...

Is there someplace I can see which appliances are targeted for debian12/ tkl18? was specifically looking for the observium container; as py2 support (deb11) is now deprecated in observium, meaning...

> Hi @wolfspyre, > > Thanks for your interest. Howdy Jeremy! I've already gotten an account spun up on the forums... you approved me a few weeks ago. I'm really...