Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #197768
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Newsgroups | alt.folklore.computers, comp.lang.python |
| Subject | Re: Don’t You Think ... |
| Date | 2026-04-23 00:07 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <10sbnr6$2kkkk$10@dont-email.me> (permalink) |
| References | <10rhm00$30efr$1@dont-email.me> |
Cross-posted to 2 groups.
On Mon, 13 Apr 2026 02:56:00 -0000 (UTC), I wrote: > ... if Bitsavers would just add a SHA-256 hash column to their > IndexByDate.txt files, that would make it so much easier to figure > out what had changed, and what had merely been moved around, without > having to access any of the actual document files? As a detailed example of what I mean, see the doc_server example script here <https://gitlab.com/ldo/inotipy_examples>. Point it at a directory full of files, and it will serve them up via the web -- of course, don’t make it directly public-facing, instead put it behind a “real” web server (e.g. Apache or Nginx) as a server-side proxy. It automatically generates IndexByDate.txt itself, it doesn’t need a file by that name in the directory tree. The key point with that example is it uses the Linux fanotify API to detect changes to the directory tree and automatically update its directory listings as well as the index.
Back to comp.lang.python | Previous | Next | Find similar
Re: Don’t You Think ... Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-04-23 00:07 +0000
csiph-web