Hi Herb,

Oddly, this is exactly the aspect to which I now turn my attention. There 
are two methods to be compared - the first is to build the static site and 
deploy the output. The second is to deploy the raw content and then run the 
build tool "in the cloud" using a 'continuous integration' method.

Either way the deploy tool du jour is 'git'; primarily a version control 
system that mirrors our changing content to a 'repository' at, for example, 
github.com. We 'push' changes to this online repo when we want to update 
our site. In the first scenario, our pushed code is the output and we're 
done. In the second, we require a further build step to be carried out. 
This is achieved via what is called a 'git hook' that will run a tool to 
build the output and deploy it as instructed.

Travis CI is one such continuous integration tool and it should be possible 
to set it up to run tiddlywiki and build the site but my preferred host is 
Netlify.com and I think their integrated tools ought to be able to do the 
same thing. Too many options, as always.

Anyway, you'll have a tutorial within a week, I promise.


On Saturday, August 12, 2017 at 8:04:47 PM UTC+10, Herb Nazhe wrote:
> On Saturday, 12 August 2017 01:48:54 UTC+3, RichardWilliamSmith wrote:
>> Tiddlywiki can be used to generate a static website where each page is in 
>> its own file.
> Excellent. One questions: can the files be generated directly on the 
> remote server (by a remotely located Tiddly generator)? Or will we have to 
> create them locally and then FTP them up?

You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
For more options, visit https://groups.google.com/d/optout.

Reply via email to