Terry Hancock @TerryHancock@mastodon.art

It might seem strange to have any rendered animation like that in the library repo, but these are stock shots in the title sequence, so it's handy to have the prerendered animation stored.

But it wasn't great dealing with the large number of files. This will make them a little easier to manage, I hope.

I did all of this on a test copy of the repo. I'm now working through the process on the copy I already uploaded to my server.

This was Roger Moore. I'm pretty sure the previous Bond movie was "Live and Let Die" and the next (from the end credits) is "For Your Eyes Only" (I remember nothing about that one, except the theme song which was all over the radio then).

There are a LOT SF callbacks in this one. They even ripped off the title font and color from "Star Wars" for the end credits. I mentioned the "Close Encounters" keypad. And the space station is strongly evocative of "2001".

But all just a little bit dumber.

Bond, is of course, his troglodyte misogynistic sexist violent self. I kind of hate him.

"Jaws" has some great comic and weirdly-sympathetic moments in this film.

The space technology is all just a little "off". They clearly had been introduced to some real concepts, but didn't quite get them right.

I was actually favorably impressed that they seemed to get the notion that "artificial gravity" on the space station had something to do with rotation, though that's about as far as they got.
...

So, of course, I absolutely loved it. I was, I suppose, about 12, then, and an extreme Trekkie -- or "Trekker" as I would've insisted at the time!

The space shuttle "Enterprise" appears in a wall-display in the recreation room in the movie. Of course, the Shuttle was in development then, and had not yet had a launch.

Seems like kind of a weird default. Probably mirroring how filter-branch works, I guess.

I can see I'm going to have a complex procedure to write up! But I am finally getting some results with Git, which is kind of a relief.

Once I get the procedure down, I'll have to repeat it on each of the 12 repos I copied up to the server, and then push them onto the Gitea server, and I should be back in business.

git-filter-repo was fairly easy to install manually, because it's just a single-file Python script.

I have a lot of "*.blend1" & "*.blend2" files taking up space in the repo that were accidentally committed and later deleted.

I did hit a "gotcha" -- that "invert-paths" switch is pretty important! It tells it to delete the paths you are specifying instead of DELETING EVERYTHING ELSE.

No "undo" for this, it's all just gone!

Oops. So I'm starting over from the top, today!

So, I started to get some useful results with "git lfs migrate" last night, after I made sure to use Git clone to create the repo I was testing on, rather than a filesystem-level copy.

Then I started learning to use "git-filter-repo" (a 3rd party Python script that is recommended as a more efficient and simpler alternative to filter-branch for whole-repo history-rewriting).

I plan to use this to strip out blob data that was committed by accident.

Actually about 2.5X less efficient.

This is probably still a win, because the LFS data will be stored in S3 object storage, which is a lot cheaper than local storage on the server.

But it's interesting. I wonder why that happens?

This at least gave me some actual results: most of the filetypes I had specified were converted to LFS storage.

One annoying thing is that the storage still grew a lot, and the growth remained after running the cleanup and garbage collection.

But the regular repo is now much smaller -- 1.1GB now. But the LFS storage is 25GB, compared to 10GB for the same data in the regular repo.

So I guess that implies the LFS storage is a little less efficient?

[...]

Okay. So I've changed a few things to try to follow the examples more closely, and I think I've got it working better.

I had previously just copied my repo to a test directory to work on it, but this time, I used Git to clone it -- so I guess that's not just a simple copy.

I also deleted all of the working files from the directory, so that only the repo itself remained.

Also, on this time, I verified that the lfs directory was empty.

[...]