My current deployment procedure is not the best. It was a quick hack that I devised just to get the ball running with the website.

After putting the finger down on the procedure to externalise image tiddlers, this unearthed an urgency to rethink the whole deployment process.

Why is this not straightforward? There are some factors in play.

— the main instance of the TiddlyWiki NodeJS server can (and should) keep the images in tiddlers. This is just simpler. (although I recognise that even the NodeJS server might benefit from not loading this content directly).

— in a way, externalising destructs the original information, because it modifies the original tiddler contents (and makes it impossible very, very hard to retrieve the externalised images in the NodeJS instance).

— the static .html files (which is what the public version of my Wiki consists of, really) must already have the externalised image URI's in place.