extra protection from data loss

[tevpg]

Am I too belt-and-braces? But if we want to genuinely use this and discard paper backup, then I think it's not a bad idea to make it as data-protective as we reasonably can.

1. new possibly best idea: save to google drive portion of the chromebook's filesystem. This assumes of course that the running system is chrome or windows (with Google Drive on it) but that works for now.

2. This thing can email a copy of its logfile to every hour or so. This would leverage something super-simple like linux package s-nail and an app pw for a gmail account. Obv would only do this if flagged to do so in config. Here fwiw are my notes on how I enabled it on my server:

Summary of what took WAY too long to figure out:
get an “app password” for the gmail account (requires turning on 2FA)
apt install s-nail
(had installed msmtp but turns out did not need it)
create ~root/.mailrc with permissions 600 (or 640):
  # This seems super minimalist but it seems to work for my purposes.
  # The pw is a gmail "App Password"
  # todd 2022-12-12
  set v15-compat
  set mta=smtp://{sender-gmail-account}:{key}@smtp.gmail.com:587 smtp-use-starttls
  set from="{Name} <sender-gmail-account@gmail.com>"
that’s it!
Example:
# echo this is body text | s-nail -a an_attachment.jpg -s “subject” some.email.address@wherever.com

3. This could check to see if there's a (particular?) USB key inserted when it saves, and if so then would save a copy onto that. Workflow thus would be: occasionally a staff member inserts CB USB key, presses enter (which does saves as we know), then removes the key

[tevpg]

Closing this as it is covered in the "PUBLISH" function, even though it (ugh) presumes working on a Chromebook. Seems that a general solution to this is unlikely since so much depends on the OS, its connections, and its configurations.