$:/tags/StartupAction/Node not executed TW5.1.20

[Torax Malu]

Hi,

I am tinkering with the bootup process and noticed that the tiddler marked with "$:/tags/StartupAction/Node" is not executed on node.js. The "server" is operated with the "new" listen-command.

Start-Parameters: tiddlywiki "Aufbau" --listen "host=[::]" "port=80"

Tiddlywiki has been installed "global".

Cheers

ToraxMalu

[PMario]

On Sunday, August 18, 2019 at 8:02:06 AM UTC+2, Torax Malu wrote:

...

Start-Parameters: tiddlywiki "Aufbau" --listen "host=[::]" "port=80"

did you try: tiddlywiki Aufbau --listen host=[::] port=80

-m

[PMario]

Hi,

You may use quotes only if there are spaces involved. Going without spaces makes everything easier.

-m

[Torax Malu]

Hi Mario. Nice try, but the quotes shouldn't effect the execution of tiddlers marked with startup-routines and indeed it is so.

Little bit more background: According documentation TW uses 3 different system tags for startup-routines. The so marked tiddlers are parsed and executed.

The tags are:

• $:/tags/StartupAction
• $:/tags/StartupAction/Browser
• $:/tags/StartupAction/Node

I created 3 tiddlers which contains a action-createtiddler-Widget.

As I expected the tiddler marked with $:/tags/StartupAction is executed twice: After start of the node.js-Server and a second time by calling TW via the browser.

The tiddler marked with $:/tags/StartupAction/Browser is executed while calling the server with the browser.

Only the tiddler marked with $:/tags/StartupAction/Node is not executed on server-startup.

So this seems to be a bug for me or I misunderstanding or miss something important.

Cheers

ToraxMalu

[PMario]

hmm,

Did you try 127.0.0.1  or ::1   which imo is localhost

-m

[Torax Malu]

Mario, there is no difference in the execution. The Server-Address [::] is simply the IPv6-Version of "0.0.0.0" and allows the call of the server via IPv4 and IPv6 from every Network-Interface. It is as mentioned:

• $:/tags/StartupAction marked tiddler is executed twice on startup of nodeJS-Server and Browser-Call
  
• $:/tags/StartupAction/Browser marked tiddler is executed on Browser-Call
  
• $:/tags/StartupAction/Node marked tiddler is never executed.

and yes, I set now the server- and client-ip to 127.0.0.1 and removed the "" around the wiki-name.

I should workaround the problem by

• placing a execution lock on the $:/tags/StartupAction-Tiddler after the first execution
• and releasing the lock with the execution of $:/tags/StartupAction/Browser-Tiddler.

But I think this is not the intention of the programmers if they implemented an special tag for the nodeJS-version of the wiki.