Difference between revisions of "2024/05/04"
(Created page with "{| width=100% style="border: solid green 1px;" |- | align=center | [start] ← 05/04 → 05/05 <big>Saturday, May 4</big> |} {{c/date|2024-05-04}} ==...") |
|||
| (5 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{| | {{page/date|Woozle's Journal}} | ||
''This is a continuation of work described in [[Woozle/blarg/2024/05/SSDying]].'' | |||
==Cleanup, Cont.== | ==Cleanup, Cont.== | ||
FTM is currently copying more stuff off the bad SSD -- and for some reason it's not running into that bad patch anymore (where it succeeds in opening the file -- the code ''does'' detect if that doesn't work -- and then gets stuck trying to read from it). Theory: it partly copied the file over, and now is detecting that the files are different sizes and skipping the copy attempt. That'll do for now. | |||
I think the next piece that needs to happen is that the conf builder needs to have some command-line options so I can tell it not to expect the environment to be right (or to create any folders) when I'm working on it locally. ...so that I can finally actually deploy the latest VbzCart demo (and then maybe work on migrating more stuff over to that Hetzlet). | I think the next piece that needs to happen is that the conf builder needs to have some command-line options so I can tell it not to expect the environment to be right (or to create any folders) when I'm working on it locally. ...so that I can finally actually deploy the latest VbzCart demo (and then maybe work on migrating more stuff over to that Hetzlet). | ||
That means integrating it with the Futilities libraries -- which should be a little easier now that I did that namespace refactoring... I hope. | That means integrating it with the Futilities libraries -- which should be a little easier now that I did that namespace refactoring... I hope. | ||
Oh: and of course at some point I need to set up ''proper'' database backups, everywhere... with some kind of notification system so I know they're working (or not). | |||
Latest revision as of 14:07, 5 May 2024
|
Saturday, May 4, 2024 (#125) Woozle's Journal
|
|
|
This is a continuation of work described in Woozle/blarg/2024/05/SSDying.
Cleanup, Cont.
FTM is currently copying more stuff off the bad SSD -- and for some reason it's not running into that bad patch anymore (where it succeeds in opening the file -- the code does detect if that doesn't work -- and then gets stuck trying to read from it). Theory: it partly copied the file over, and now is detecting that the files are different sizes and skipping the copy attempt. That'll do for now.
I think the next piece that needs to happen is that the conf builder needs to have some command-line options so I can tell it not to expect the environment to be right (or to create any folders) when I'm working on it locally. ...so that I can finally actually deploy the latest VbzCart demo (and then maybe work on migrating more stuff over to that Hetzlet).
That means integrating it with the Futilities libraries -- which should be a little easier now that I did that namespace refactoring... I hope.
Oh: and of course at some point I need to set up proper database backups, everywhere... with some kind of notification system so I know they're working (or not).