Re: [tw5] Re: Best approach for multiple wikis

[Mohammad]

Thanks I will have a look!

On Monday, December 9, 2019 at 4:39:08 PM UTC+3:30, Arlen Beiler wrote:
>
> src/generateDirectoryListing.js
>
> On Sun, Dec 8, 2019 at 2:01 AM Mohammad  > wrote:
>
>> Hi Arlen,
>>  Where is the landing page of TiddlyServer!
>> I gonna to give try if I can use TW for landing page!
>>
>> --Mohammad
>>
>> On Tuesday, December 3, 2019 at 11:30:43 PM UTC+3:30, Arlen Beiler wrote:
>>>
>>> Just thought I'd take a minute to chime in here. I made TiddlyServer to 
>>> solve my own problem of Massive Multi-file Online wikis. It serves the 
>>> folders you specify in a sort of tree allowing them to be grouped together 
>>> and easily navigated with the built-in directory index (even the virtual 
>>> directories or "groups"). When a data folder is accessed, TiddlyServer 
>>> automatically fires up a node instance of the TiddlyWiki listen command and 
>>> mounts it at that path, meaning it forwards all requests to the data folder 
>>> Node server instance. This makes it work identical to the TiddlyWiki listen 
>>> command for most normal uses of the listen command, except you can access 
>>> multiple data folders on the same server. Single file wikis (TW 5.1.15 and 
>>> newer) have a saver already built into them which TiddlyServer uses to save 
>>> single file wikis. Single file wikis can be backed up automatically on 
>>> every save, but data folders are on their own by design. I recommend 
>>> using Git or Dropbox for that. 
>>>
>>> There are a bunch of advanced options and even authentication, but the 
>>> basics are enough for most people. 
>>>
>>> It's pretty simple to use but I often notice people having trouble 
>>> getting it installed, so I thought I'd throw in some install instructions I 
>>> wrote some time ago. 
>>>
>>> It's fine to just use master (well, aka v2.1 right now) right now: 
>>> https://github.com/Arlen22/TiddlyServer -- Click the green "Clone or 
>>> Download" button then select your preferred download method. Cloning the 
>>> repo is an easy way to get updates but downloading is fine too. 
>>>
>>> Extract it to an empty folder so you don't risk merging with an existing 
>>> folder. Once you extract it you can move it wherever you want it to be. 
>>>
>>> https://nodejs.org/en/
>>>
>>> Go to NodeJS.org and download the LTS version of Node, which currently 
>>> is 10.x, and install it on the computer you will be running TiddlyServer 
>>> on. It's pretty straightforward, and the default options should work fine. 
>>>
>>> You don't actually need to install the whole thing, you can also just 
>>> download a zip file and extract node.exe into the TiddlyServer folder to 
>>> make a portable install. Since you're working with IIS I'm sure you have 
>>> enough computer experience know what I'm talking about, but if I'm not 
>>> making myself clear, just install NodeJS like I described above. 
>>>
>>> Now, here's the part that most people find tricky. Copy 
>>> example-settings-quick.json and name it settings.json. That's the simplest 
>>> setup. You can change the tree property to change what folders get served, 
>>> but all html files and data folders inside it should just work out of the 
>>> box. 
>>>
>>> The entire documentation for the settings.json file is at 
>>> https://arlen22.github.io/tiddlyserver/docs/serverconfig.html and the 
>>> tree property is the first item on the page. Here's a really simple example 
>>> to get you started. 
>>>
>>> "tree": {
>>> "myfolder": "../personal",
>>> "workstuff": "../work",
>>> "user": "~/Desktop/random",
>>> "projects_group": {
>>> "tiddlyserver": "~/Desktop/Github/TiddlyServer",
>>> "material-theme": "~/Dropbox/Material Theme"
>>> }
>>> }
>>>
>>>
>>> And that's all there is to it. Once you have your settings.json file 
>>> setup, just run "node server.js" to start the server. TiddlyServer expects 
>>> to find the settings.json file in the same directory (which is where I have 
>>> mine, which is why it's in .gitignore!).
>>>
>>> I made TiddlyServer simple because I want it to be simple for me to use 
>>> every day :) 
>>>
>>> Hope that helps 
>>>
>>> On Tue, Dec 3, 2019 at 9:02 AM Victor Dorneanu  wrote:
>>>
 Hi TT,

 it's not really related to Github. I just use to store/backup my 
 tiddlers. The backend storage is actually quite irrelevant. I just need 
 some "best practices" / workflows that individuals have established over 
 time in order to manage multiple wikis. 

 Cheers, 
 Victor

 On Tuesday, December 3, 2019 at 12:26:32 PM UTC+1, TiddlyTweeter wrote:
>
> Ciao Victor
>
> As far as I understand GitHub it can be used (with various sub-tools) 
> to create workflows of complexity & sophistication.
>
> I don't have the knowledge to advise on particulars. 
>
> But I think this may be more a question for asking on GitHub itself?
>
> Best wishes
> TT
>
> On Monday, 2 December 2019 11:39:56 UTC+1, Victor Dorneanu wrote:
>>

Re: [tw5] Re: Best approach for multiple wikis

[Arlen Beiler]

sometimes browsers let you send script tags after the html tag is closed,
you could try inserting the directory entries in there. I use vscode, which
will give you intellisense help. I also recommend running npm install which
should give you the same npm dependancies as I use. Hopefully everything's
configured correctly. If it says it can't find a module, just let me know.

On Mon, Dec 9, 2019 at 8:08 AM Arlen Beiler  wrote:

> src/generateDirectoryListing.js
>
> On Sun, Dec 8, 2019 at 2:01 AM Mohammad 
> wrote:
>
>> Hi Arlen,
>>  Where is the landing page of TiddlyServer!
>> I gonna to give try if I can use TW for landing page!
>>
>> --Mohammad
>>
>> On Tuesday, December 3, 2019 at 11:30:43 PM UTC+3:30, Arlen Beiler wrote:
>>>
>>> Just thought I'd take a minute to chime in here. I made TiddlyServer to
>>> solve my own problem of Massive Multi-file Online wikis. It serves the
>>> folders you specify in a sort of tree allowing them to be grouped together
>>> and easily navigated with the built-in directory index (even the virtual
>>> directories or "groups"). When a data folder is accessed, TiddlyServer
>>> automatically fires up a node instance of the TiddlyWiki listen command and
>>> mounts it at that path, meaning it forwards all requests to the data folder
>>> Node server instance. This makes it work identical to the TiddlyWiki listen
>>> command for most normal uses of the listen command, except you can access
>>> multiple data folders on the same server. Single file wikis (TW 5.1.15 and
>>> newer) have a saver already built into them which TiddlyServer uses to save
>>> single file wikis. Single file wikis can be backed up automatically on
>>> every save, but data folders are on their own by design. I recommend
>>> using Git or Dropbox for that.
>>>
>>> There are a bunch of advanced options and even authentication, but the
>>> basics are enough for most people.
>>>
>>> It's pretty simple to use but I often notice people having trouble
>>> getting it installed, so I thought I'd throw in some install instructions I
>>> wrote some time ago.
>>>
>>> It's fine to just use master (well, aka v2.1 right now) right now:
>>> https://github.com/Arlen22/TiddlyServer -- Click the green "Clone or
>>> Download" button then select your preferred download method. Cloning the
>>> repo is an easy way to get updates but downloading is fine too.
>>>
>>> Extract it to an empty folder so you don't risk merging with an existing
>>> folder. Once you extract it you can move it wherever you want it to be.
>>>
>>> https://nodejs.org/en/
>>>
>>> Go to NodeJS.org and download the LTS version of Node, which currently
>>> is 10.x, and install it on the computer you will be running TiddlyServer
>>> on. It's pretty straightforward, and the default options should work fine.
>>>
>>> You don't actually need to install the whole thing, you can also just
>>> download a zip file and extract node.exe into the TiddlyServer folder to
>>> make a portable install. Since you're working with IIS I'm sure you have
>>> enough computer experience know what I'm talking about, but if I'm not
>>> making myself clear, just install NodeJS like I described above.
>>>
>>> Now, here's the part that most people find tricky. Copy
>>> example-settings-quick.json and name it settings.json. That's the simplest
>>> setup. You can change the tree property to change what folders get served,
>>> but all html files and data folders inside it should just work out of the
>>> box.
>>>
>>> The entire documentation for the settings.json file is at
>>> https://arlen22.github.io/tiddlyserver/docs/serverconfig.html and the
>>> tree property is the first item on the page. Here's a really simple example
>>> to get you started.
>>>
>>> "tree": {
>>> "myfolder": "../personal",
>>> "workstuff": "../work",
>>> "user": "~/Desktop/random",
>>> "projects_group": {
>>> "tiddlyserver": "~/Desktop/Github/TiddlyServer",
>>> "material-theme": "~/Dropbox/Material Theme"
>>> }
>>> }
>>>
>>>
>>> And that's all there is to it. Once you have your settings.json file
>>> setup, just run "node server.js" to start the server. TiddlyServer expects
>>> to find the settings.json file in the same directory (which is where I have
>>> mine, which is why it's in .gitignore!).
>>>
>>> I made TiddlyServer simple because I want it to be simple for me to use
>>> every day :)
>>>
>>> Hope that helps
>>>
>>> On Tue, Dec 3, 2019 at 9:02 AM Victor Dorneanu  wrote:
>>>
 Hi TT,

 it's not really related to Github. I just use to store/backup my
 tiddlers. The backend storage is actually quite irrelevant. I just need
 some "best practices" / workflows that individuals have established over
 time in order to manage multiple wikis.

 Cheers,
 Victor

 On Tuesday, December 3, 2019 at 12:26:32 PM UTC+1, TiddlyTweeter wrote:
>
> Ciao Victor
>
> As far as I understand GitHub it can be used (with various sub-tools)
> to create workflows of complexity & 

Re: [tw5] Re: Best approach for multiple wikis

[Arlen Beiler]

src/generateDirectoryListing.js

On Sun, Dec 8, 2019 at 2:01 AM Mohammad  wrote:

> Hi Arlen,
>  Where is the landing page of TiddlyServer!
> I gonna to give try if I can use TW for landing page!
>
> --Mohammad
>
> On Tuesday, December 3, 2019 at 11:30:43 PM UTC+3:30, Arlen Beiler wrote:
>>
>> Just thought I'd take a minute to chime in here. I made TiddlyServer to
>> solve my own problem of Massive Multi-file Online wikis. It serves the
>> folders you specify in a sort of tree allowing them to be grouped together
>> and easily navigated with the built-in directory index (even the virtual
>> directories or "groups"). When a data folder is accessed, TiddlyServer
>> automatically fires up a node instance of the TiddlyWiki listen command and
>> mounts it at that path, meaning it forwards all requests to the data folder
>> Node server instance. This makes it work identical to the TiddlyWiki listen
>> command for most normal uses of the listen command, except you can access
>> multiple data folders on the same server. Single file wikis (TW 5.1.15 and
>> newer) have a saver already built into them which TiddlyServer uses to save
>> single file wikis. Single file wikis can be backed up automatically on
>> every save, but data folders are on their own by design. I recommend
>> using Git or Dropbox for that.
>>
>> There are a bunch of advanced options and even authentication, but the
>> basics are enough for most people.
>>
>> It's pretty simple to use but I often notice people having trouble
>> getting it installed, so I thought I'd throw in some install instructions I
>> wrote some time ago.
>>
>> It's fine to just use master (well, aka v2.1 right now) right now:
>> https://github.com/Arlen22/TiddlyServer -- Click the green "Clone or
>> Download" button then select your preferred download method. Cloning the
>> repo is an easy way to get updates but downloading is fine too.
>>
>> Extract it to an empty folder so you don't risk merging with an existing
>> folder. Once you extract it you can move it wherever you want it to be.
>>
>> https://nodejs.org/en/
>>
>> Go to NodeJS.org and download the LTS version of Node, which currently is
>> 10.x, and install it on the computer you will be running TiddlyServer on.
>> It's pretty straightforward, and the default options should work fine.
>>
>> You don't actually need to install the whole thing, you can also just
>> download a zip file and extract node.exe into the TiddlyServer folder to
>> make a portable install. Since you're working with IIS I'm sure you have
>> enough computer experience know what I'm talking about, but if I'm not
>> making myself clear, just install NodeJS like I described above.
>>
>> Now, here's the part that most people find tricky. Copy
>> example-settings-quick.json and name it settings.json. That's the simplest
>> setup. You can change the tree property to change what folders get served,
>> but all html files and data folders inside it should just work out of the
>> box.
>>
>> The entire documentation for the settings.json file is at
>> https://arlen22.github.io/tiddlyserver/docs/serverconfig.html and the
>> tree property is the first item on the page. Here's a really simple example
>> to get you started.
>>
>> "tree": {
>> "myfolder": "../personal",
>> "workstuff": "../work",
>> "user": "~/Desktop/random",
>> "projects_group": {
>> "tiddlyserver": "~/Desktop/Github/TiddlyServer",
>> "material-theme": "~/Dropbox/Material Theme"
>> }
>> }
>>
>>
>> And that's all there is to it. Once you have your settings.json file
>> setup, just run "node server.js" to start the server. TiddlyServer expects
>> to find the settings.json file in the same directory (which is where I have
>> mine, which is why it's in .gitignore!).
>>
>> I made TiddlyServer simple because I want it to be simple for me to use
>> every day :)
>>
>> Hope that helps
>>
>> On Tue, Dec 3, 2019 at 9:02 AM Victor Dorneanu  wrote:
>>
>>> Hi TT,
>>>
>>> it's not really related to Github. I just use to store/backup my
>>> tiddlers. The backend storage is actually quite irrelevant. I just need
>>> some "best practices" / workflows that individuals have established over
>>> time in order to manage multiple wikis.
>>>
>>> Cheers,
>>> Victor
>>>
>>> On Tuesday, December 3, 2019 at 12:26:32 PM UTC+1, TiddlyTweeter wrote:

 Ciao Victor

 As far as I understand GitHub it can be used (with various sub-tools)
 to create workflows of complexity & sophistication.

 I don't have the knowledge to advise on particulars.

 But I think this may be more a question for asking on GitHub itself?

 Best wishes
 TT

 On Monday, 2 December 2019 11:39:56 UTC+1, Victor Dorneanu wrote:
>
> Hi everyone,
>
> what I want to achieve is to have multiple wikis for each "area" of
> knowledge. Let's say:
>
>
>- coding
>- notes (from books, articles etc.)
>- cooking recipes
>- etc.
>
>
> I like to 

Re: [tw5] Re: Best approach for multiple wikis

[Mohammad]

Hi Arlen,
 Where is the landing page of TiddlyServer!
I gonna to give try if I can use TW for landing page!

--Mohammad

On Tuesday, December 3, 2019 at 11:30:43 PM UTC+3:30, Arlen Beiler wrote:
>
> Just thought I'd take a minute to chime in here. I made TiddlyServer to 
> solve my own problem of Massive Multi-file Online wikis. It serves the 
> folders you specify in a sort of tree allowing them to be grouped together 
> and easily navigated with the built-in directory index (even the virtual 
> directories or "groups"). When a data folder is accessed, TiddlyServer 
> automatically fires up a node instance of the TiddlyWiki listen command and 
> mounts it at that path, meaning it forwards all requests to the data folder 
> Node server instance. This makes it work identical to the TiddlyWiki listen 
> command for most normal uses of the listen command, except you can access 
> multiple data folders on the same server. Single file wikis (TW 5.1.15 and 
> newer) have a saver already built into them which TiddlyServer uses to save 
> single file wikis. Single file wikis can be backed up automatically on 
> every save, but data folders are on their own by design. I recommend 
> using Git or Dropbox for that. 
>
> There are a bunch of advanced options and even authentication, but the 
> basics are enough for most people. 
>
> It's pretty simple to use but I often notice people having trouble getting 
> it installed, so I thought I'd throw in some install instructions I wrote 
> some time ago. 
>
> It's fine to just use master (well, aka v2.1 right now) right now: 
> https://github.com/Arlen22/TiddlyServer -- Click the green "Clone or 
> Download" button then select your preferred download method. Cloning the 
> repo is an easy way to get updates but downloading is fine too. 
>
> Extract it to an empty folder so you don't risk merging with an existing 
> folder. Once you extract it you can move it wherever you want it to be. 
>
> https://nodejs.org/en/
>
> Go to NodeJS.org and download the LTS version of Node, which currently is 
> 10.x, and install it on the computer you will be running TiddlyServer on. 
> It's pretty straightforward, and the default options should work fine. 
>
> You don't actually need to install the whole thing, you can also just 
> download a zip file and extract node.exe into the TiddlyServer folder to 
> make a portable install. Since you're working with IIS I'm sure you have 
> enough computer experience know what I'm talking about, but if I'm not 
> making myself clear, just install NodeJS like I described above. 
>
> Now, here's the part that most people find tricky. Copy 
> example-settings-quick.json and name it settings.json. That's the simplest 
> setup. You can change the tree property to change what folders get served, 
> but all html files and data folders inside it should just work out of the 
> box. 
>
> The entire documentation for the settings.json file is at 
> https://arlen22.github.io/tiddlyserver/docs/serverconfig.html and the 
> tree property is the first item on the page. Here's a really simple example 
> to get you started. 
>
> "tree": {
> "myfolder": "../personal",
> "workstuff": "../work",
> "user": "~/Desktop/random",
> "projects_group": {
> "tiddlyserver": "~/Desktop/Github/TiddlyServer",
> "material-theme": "~/Dropbox/Material Theme"
> }
> }
>
>
> And that's all there is to it. Once you have your settings.json file 
> setup, just run "node server.js" to start the server. TiddlyServer expects 
> to find the settings.json file in the same directory (which is where I have 
> mine, which is why it's in .gitignore!).
>
> I made TiddlyServer simple because I want it to be simple for me to use 
> every day :) 
>
> Hope that helps 
>
> On Tue, Dec 3, 2019 at 9:02 AM Victor Dorneanu  > wrote:
>
>> Hi TT,
>>
>> it's not really related to Github. I just use to store/backup my 
>> tiddlers. The backend storage is actually quite irrelevant. I just need 
>> some "best practices" / workflows that individuals have established over 
>> time in order to manage multiple wikis. 
>>
>> Cheers, 
>> Victor
>>
>> On Tuesday, December 3, 2019 at 12:26:32 PM UTC+1, TiddlyTweeter wrote:
>>>
>>> Ciao Victor
>>>
>>> As far as I understand GitHub it can be used (with various sub-tools) to 
>>> create workflows of complexity & sophistication.
>>>
>>> I don't have the knowledge to advise on particulars. 
>>>
>>> But I think this may be more a question for asking on GitHub itself?
>>>
>>> Best wishes
>>> TT
>>>
>>> On Monday, 2 December 2019 11:39:56 UTC+1, Victor Dorneanu wrote:

 Hi everyone, 

 what I want to achieve is to have multiple wikis for each "area" of 
 knowledge. Let's say:


- coding
- notes (from books, articles etc.)
- cooking recipes
- etc.


 I like to manage my tiddlers at a single place, that means: Have 
 everything inside a big (git) repository. However, when I want to 
 share/publish my 

Re: [tw5] Re: Best approach for multiple wikis

['Mark S.' via TiddlyWiki]

Disabling etag has made a major improvement in performance.

On Thursday, December 5, 2019 at 5:34:11 PM UTC-8, Arlen Beiler wrote:
>
> In this case the etag, while basically the same idea, is handled by the 
> browser-side TiddlyWiki and is stored in the pages JavaScript, so it isn't 
> affected by the cache. This problem is usually server-side or disk-side -- 
> its rarely related to the browser. 
>
> On Thu, Dec 5, 2019 at 4:25 PM 'Mark S.' via TiddlyWiki <
> tiddl...@googlegroups.com > wrote:
>
>> After speed-reading wikipedia, it seems to me that if the browser's cache 
>> doesn't update correctly, it might hang on to a 6 hour old etag value. I've 
>> noticed firefox doing this in other capacities. For instance, after 
>> reloading a list of my current reading, items that were previously 
>> unchecked will still show. I will have to load the page a second time in 
>> order to display the correct values.
>>
>> On Thursday, December 5, 2019 at 1:11:21 PM UTC-8, Mark S. wrote:
>>>
>>> I think I need an explainer about what an "etag" is. There are etags in 
>>> the vim editor, but I don't think you mean the same thing.
>>>
>>> Just to repeat. Between one save and a second attempted save was more 
>>> like 6 minutes, not 6 hours. But I don't understand what the etag is and 
>>> how it gets set.
>>>
>>> Thanks!
>>>
>>> On Thursday, December 5, 2019 at 12:55:52 PM UTC-8, Arlen Beiler wrote:

 You can disable etag checking completely if you want. If you can 
 include some more examples from the log file that would be great as well. 

 The relevant log file info here shows the two values, ifmatch being the 
 browser copy. The last number is the modified timestamp in milliseconds, 
 which as you can see in this case are 6 hours apart. If you google 
 "epoch converter" you can paste that into "1970 Epoch in Milliseconds" 
 converter to get the date. The third line (and similar lines in more 
 serious scenarios) are debug lines where TiddlyServer points out which 
 parts are different and caused the etag to fail. 

 412 ifmatch "0-5124547-*1575414313000*"
 412 etag "0-5124547-*1575434388000*"
 *412 caused by difference in modified*
 [2019-12-03T20:46:07.125-0800] PUT 127.0.0.1   412 127.0.0.1 
 /TW2014/T
 o.html   42.922 ms - -

 The docs for the putsaver.etag setting is here: 
 https://arlen22.github.io/tiddlyserver/docs/serverconfig.html#etag-string 
 

 The section docs 
 https://arlen22.github.io/tiddlyserver/docs/serverconfig.html#section-putsaver
  has 
 an example snippet. 

 Alternatively, you can set etagAge (which is seconds, default of 3) to 
 a ridiculously high number (like 2 hours) so it only checks the size and 
 not the timestamp. But remember that the etag is gotten when the file is 
 loaded, so even if it sits in your browser for six hours, it will still be 
 the same if the file has not been modified on disk since then. There are 
 various reasons why this could happen, which is why I added the etagAge 
 setting. Another user had the same problem and we thought it seemed like 
 the antivirus was changing the modified timestamp on certain drives for 
 some reason. 

 Hope that helps.
 Arlen

 On Wed, Dec 4, 2019 at 11:07 AM 'Mark S.' via TiddlyWiki <
 tiddl...@googlegroups.com> wrote:

> Unless my computer has discovered time travel, there is no way the 
> file on disk is 6 hours newer.
>
> I load.
> I save once.
> I do things in the TW
> I save again ... and get the error.
>
> So unless the file was saved with a timestamp 6 hours in the future, 
> it should be several minutes *older* than the browser version at the time 
> of the save.
>
> I'm using 5.1.21
>
> I'm wondering why it checks the time at all. Unless I do something 
> crazy like manually copy a different version to the directory, the 
> browser 
> version should be "king".
>
> Perhaps checking the date slows things down. It's noticeably slower 
> saving a single-file wiki with TS than with BobSaver or file-backups.
>
> Thanks!
>
> On Wednesday, December 4, 2019 at 7:19:38 AM UTC-8, Arlen Beiler wrote:
>>
>> In this particular case, the file on disk is 6 hours newer than the 
>> copy the browser downloaded. I have not used this feature of 
>> TiddlyServer 
>> much so perhaps I should take a look at it again, but nothing changed 
>> since 
>> I made it that I know of. I did run into a scenario where the etag was 
>> changing by a second or two, so I added the putsaver.etagAge option to 
>> set 
>> the window within which to 

Re: [tw5] Re: Best approach for multiple wikis

[Arlen Beiler]

In this case the etag, while basically the same idea, is handled by the
browser-side TiddlyWiki and is stored in the pages JavaScript, so it isn't
affected by the cache. This problem is usually server-side or disk-side --
its rarely related to the browser.

On Thu, Dec 5, 2019 at 4:25 PM 'Mark S.' via TiddlyWiki <
tiddlywiki@googlegroups.com> wrote:

> After speed-reading wikipedia, it seems to me that if the browser's cache
> doesn't update correctly, it might hang on to a 6 hour old etag value. I've
> noticed firefox doing this in other capacities. For instance, after
> reloading a list of my current reading, items that were previously
> unchecked will still show. I will have to load the page a second time in
> order to display the correct values.
>
> On Thursday, December 5, 2019 at 1:11:21 PM UTC-8, Mark S. wrote:
>>
>> I think I need an explainer about what an "etag" is. There are etags in
>> the vim editor, but I don't think you mean the same thing.
>>
>> Just to repeat. Between one save and a second attempted save was more
>> like 6 minutes, not 6 hours. But I don't understand what the etag is and
>> how it gets set.
>>
>> Thanks!
>>
>> On Thursday, December 5, 2019 at 12:55:52 PM UTC-8, Arlen Beiler wrote:
>>>
>>> You can disable etag checking completely if you want. If you can include
>>> some more examples from the log file that would be great as well.
>>>
>>> The relevant log file info here shows the two values, ifmatch being the
>>> browser copy. The last number is the modified timestamp in milliseconds,
>>> which as you can see in this case are 6 hours apart. If you google
>>> "epoch converter" you can paste that into "1970 Epoch in Milliseconds"
>>> converter to get the date. The third line (and similar lines in more
>>> serious scenarios) are debug lines where TiddlyServer points out which
>>> parts are different and caused the etag to fail.
>>>
>>> 412 ifmatch "0-5124547-*1575414313000*"
>>> 412 etag "0-5124547-*1575434388000*"
>>> *412 caused by difference in modified*
>>> [2019-12-03T20:46:07.125-0800] PUT 127.0.0.1   412 127.0.0.1
>>> /TW2014/T
>>> o.html   42.922 ms - -
>>>
>>> The docs for the putsaver.etag setting is here:
>>> https://arlen22.github.io/tiddlyserver/docs/serverconfig.html#etag-string
>>> 
>>>
>>> The section docs
>>> https://arlen22.github.io/tiddlyserver/docs/serverconfig.html#section-putsaver
>>>  has
>>> an example snippet.
>>>
>>> Alternatively, you can set etagAge (which is seconds, default of 3) to a
>>> ridiculously high number (like 2 hours) so it only checks the size and not
>>> the timestamp. But remember that the etag is gotten when the file is
>>> loaded, so even if it sits in your browser for six hours, it will still be
>>> the same if the file has not been modified on disk since then. There are
>>> various reasons why this could happen, which is why I added the etagAge
>>> setting. Another user had the same problem and we thought it seemed like
>>> the antivirus was changing the modified timestamp on certain drives for
>>> some reason.
>>>
>>> Hope that helps.
>>> Arlen
>>>
>>> On Wed, Dec 4, 2019 at 11:07 AM 'Mark S.' via TiddlyWiki <
>>> tiddl...@googlegroups.com> wrote:
>>>
 Unless my computer has discovered time travel, there is no way the file
 on disk is 6 hours newer.

 I load.
 I save once.
 I do things in the TW
 I save again ... and get the error.

 So unless the file was saved with a timestamp 6 hours in the future, it
 should be several minutes *older* than the browser version at the time of
 the save.

 I'm using 5.1.21

 I'm wondering why it checks the time at all. Unless I do something
 crazy like manually copy a different version to the directory, the browser
 version should be "king".

 Perhaps checking the date slows things down. It's noticeably slower
 saving a single-file wiki with TS than with BobSaver or file-backups.

 Thanks!

 On Wednesday, December 4, 2019 at 7:19:38 AM UTC-8, Arlen Beiler wrote:
>
> In this particular case, the file on disk is 6 hours newer than the
> copy the browser downloaded. I have not used this feature of TiddlyServer
> much so perhaps I should take a look at it again, but nothing changed 
> since
> I made it that I know of. I did run into a scenario where the etag was
> changing by a second or two, so I added the putsaver.etagAge option to set
> the window within which to ignore it. I will check the code to make sure
> everything looks good on my end. What version of TiddlyWiki is the file?
>
> On Tue, Dec 3, 2019 at 11:53 PM 'Mark S.' via TiddlyWiki <
> tiddl...@googlegroups.com> wrote:
>
>> I get "changed on server" messages regularly.  Often on the 

Re: [tw5] Re: Best approach for multiple wikis

[Arlen Beiler]

Yes, user-relative paths use the NodeJS os module to get the user's home
directory. All other paths use NodeJS path.resolve, with the absolute path
to the settings.json file as the first argument, which means that if NodeJS
path module thinks a path is not absolute, it will use settings.json as the
source for the relative path.

On Thu, Dec 5, 2019 at 4:23 PM Mohammad  wrote:

> Hi Arlen,
>
> More feedback
>
> I understood that we can keep TiddlyServer2.1 in separate folder from
> setting.json. So I think the below description may be helpful for new users
>
> --On Windows 10
>
>
>- After testing TiddlyServer one can have a setting directory to keep
>*setting.json*
>- The setting folder (directory) can be placed any where like
>"C:\Users\Mohammad\Documents" (Mohammad can be another name for other user)
>- In the setting directory one can have a batch file to start the
>server like *startServer.cmd* as below
>
> REM TiddlyServer 2.1
>
> node D:\TiddlyServer-2.1\server.js settings.json
>
>
>- Other folder can be in the parent folder of setting directory
>
> Example:
>  If the setting.json is locted under C:\TW\TiddlyServer2.1 then
>
> -- C:
>  TW
> -- TiddlyServer
> -- *setting.js*
> ---*startServer.cmd*
> -- Personal
> ---Working
> ---Sandbox
> ---backups
>
> This is while TiddlerServer itself is located in C:\Program
> Files\TiddlyServer2.1
> Dont forget backups which is used to backup single file wikis
>
> One question:
>
> I see Tiddlyserver knows path like ~\Desktop? Does it also recognize
> absolute path?
>
>
> --Mohammad
>
>
>
> On Tuesday, December 3, 2019 at 11:30:43 PM UTC+3:30, Arlen Beiler wrote:
>>
>> Just thought I'd take a minute to chime in here. I made TiddlyServer to
>> solve my own problem of Massive Multi-file Online wikis. It serves the
>> folders you specify in a sort of tree allowing them to be grouped together
>> and easily navigated with the built-in directory index (even the virtual
>> directories or "groups"). When a data folder is accessed, TiddlyServer
>> automatically fires up a node instance of the TiddlyWiki listen command and
>> mounts it at that path, meaning it forwards all requests to the data folder
>> Node server instance. This makes it work identical to the TiddlyWiki listen
>> command for most normal uses of the listen command, except you can access
>> multiple data folders on the same server. Single file wikis (TW 5.1.15 and
>> newer) have a saver already built into them which TiddlyServer uses to save
>> single file wikis. Single file wikis can be backed up automatically on
>> every save, but data folders are on their own by design. I recommend
>> using Git or Dropbox for that.
>>
>> There are a bunch of advanced options and even authentication, but the
>> basics are enough for most people.
>>
>> It's pretty simple to use but I often notice people having trouble
>> getting it installed, so I thought I'd throw in some install instructions I
>> wrote some time ago.
>>
>> It's fine to just use master (well, aka v2.1 right now) right now:
>> https://github.com/Arlen22/TiddlyServer -- Click the green "Clone or
>> Download" button then select your preferred download method. Cloning the
>> repo is an easy way to get updates but downloading is fine too.
>>
>> Extract it to an empty folder so you don't risk merging with an existing
>> folder. Once you extract it you can move it wherever you want it to be.
>>
>> https://nodejs.org/en/
>>
>> Go to NodeJS.org and download the LTS version of Node, which currently is
>> 10.x, and install it on the computer you will be running TiddlyServer on.
>> It's pretty straightforward, and the default options should work fine.
>>
>> You don't actually need to install the whole thing, you can also just
>> download a zip file and extract node.exe into the TiddlyServer folder to
>> make a portable install. Since you're working with IIS I'm sure you have
>> enough computer experience know what I'm talking about, but if I'm not
>> making myself clear, just install NodeJS like I described above.
>>
>> Now, here's the part that most people find tricky. Copy
>> example-settings-quick.json and name it settings.json. That's the simplest
>> setup. You can change the tree property to change what folders get served,
>> but all html files and data folders inside it should just work out of the
>> box.
>>
>> The entire documentation for the settings.json file is at
>> https://arlen22.github.io/tiddlyserver/docs/serverconfig.html and the
>> tree property is the first item on the page. Here's a really simple example
>> to get you started.
>>
>> "tree": {
>> "myfolder": "../personal",
>> "workstuff": "../work",
>> "user": "~/Desktop/random",
>> "projects_group": {
>> "tiddlyserver": "~/Desktop/Github/TiddlyServer",
>> "material-theme": "~/Dropbox/Material Theme"
>> }
>> }
>>
>>
>> And that's all there is to it. Once you have your settings.json file
>> setup, just run "node server.js" to start 

Re: [tw5] Re: Best approach for multiple wikis

['Mark S.' via TiddlyWiki]

After speed-reading wikipedia, it seems to me that if the browser's cache 
doesn't update correctly, it might hang on to a 6 hour old etag value. I've 
noticed firefox doing this in other capacities. For instance, after 
reloading a list of my current reading, items that were previously 
unchecked will still show. I will have to load the page a second time in 
order to display the correct values.

On Thursday, December 5, 2019 at 1:11:21 PM UTC-8, Mark S. wrote:
>
> I think I need an explainer about what an "etag" is. There are etags in 
> the vim editor, but I don't think you mean the same thing.
>
> Just to repeat. Between one save and a second attempted save was more like 
> 6 minutes, not 6 hours. But I don't understand what the etag is and how it 
> gets set.
>
> Thanks!
>
> On Thursday, December 5, 2019 at 12:55:52 PM UTC-8, Arlen Beiler wrote:
>>
>> You can disable etag checking completely if you want. If you can include 
>> some more examples from the log file that would be great as well. 
>>
>> The relevant log file info here shows the two values, ifmatch being the 
>> browser copy. The last number is the modified timestamp in milliseconds, 
>> which as you can see in this case are 6 hours apart. If you google 
>> "epoch converter" you can paste that into "1970 Epoch in Milliseconds" 
>> converter to get the date. The third line (and similar lines in more 
>> serious scenarios) are debug lines where TiddlyServer points out which 
>> parts are different and caused the etag to fail. 
>>
>> 412 ifmatch "0-5124547-*1575414313000*"
>> 412 etag "0-5124547-*1575434388000*"
>> *412 caused by difference in modified*
>> [2019-12-03T20:46:07.125-0800] PUT 127.0.0.1   412 127.0.0.1 
>> /TW2014/T
>> o.html   42.922 ms - -
>>
>> The docs for the putsaver.etag setting is here: 
>> https://arlen22.github.io/tiddlyserver/docs/serverconfig.html#etag-string 
>> 
>>
>> The section docs 
>> https://arlen22.github.io/tiddlyserver/docs/serverconfig.html#section-putsaver
>>  has 
>> an example snippet. 
>>
>> Alternatively, you can set etagAge (which is seconds, default of 3) to a 
>> ridiculously high number (like 2 hours) so it only checks the size and not 
>> the timestamp. But remember that the etag is gotten when the file is 
>> loaded, so even if it sits in your browser for six hours, it will still be 
>> the same if the file has not been modified on disk since then. There are 
>> various reasons why this could happen, which is why I added the etagAge 
>> setting. Another user had the same problem and we thought it seemed like 
>> the antivirus was changing the modified timestamp on certain drives for 
>> some reason. 
>>
>> Hope that helps.
>> Arlen
>>
>> On Wed, Dec 4, 2019 at 11:07 AM 'Mark S.' via TiddlyWiki <
>> tiddl...@googlegroups.com> wrote:
>>
>>> Unless my computer has discovered time travel, there is no way the file 
>>> on disk is 6 hours newer.
>>>
>>> I load.
>>> I save once.
>>> I do things in the TW
>>> I save again ... and get the error.
>>>
>>> So unless the file was saved with a timestamp 6 hours in the future, it 
>>> should be several minutes *older* than the browser version at the time of 
>>> the save.
>>>
>>> I'm using 5.1.21
>>>
>>> I'm wondering why it checks the time at all. Unless I do something crazy 
>>> like manually copy a different version to the directory, the browser 
>>> version should be "king".
>>>
>>> Perhaps checking the date slows things down. It's noticeably slower 
>>> saving a single-file wiki with TS than with BobSaver or file-backups.
>>>
>>> Thanks!
>>>
>>> On Wednesday, December 4, 2019 at 7:19:38 AM UTC-8, Arlen Beiler wrote:

 In this particular case, the file on disk is 6 hours newer than the 
 copy the browser downloaded. I have not used this feature of TiddlyServer 
 much so perhaps I should take a look at it again, but nothing changed 
 since 
 I made it that I know of. I did run into a scenario where the etag was 
 changing by a second or two, so I added the putsaver.etagAge option to set 
 the window within which to ignore it. I will check the code to make sure 
 everything looks good on my end. What version of TiddlyWiki is the file?

 On Tue, Dec 3, 2019 at 11:53 PM 'Mark S.' via TiddlyWiki <
 tiddl...@googlegroups.com> wrote:

> I get "changed on server" messages regularly.  Often on the second 
> time I attempt to save. Talking single files.
> This didn't happen with the old (1.??) version. It's made it pretty 
> hard to use, since every time it happens I
> have to do a "rescue" of the changed tiddlers. If it just ignored the 
> non-existent changes on disk and saved
> it would be fine. Output below.
>
> 412 ifmatch "0-5124547-1575414313000"
> 412 etag 

Re: [tw5] Re: Best approach for multiple wikis

[Mohammad]

Hi Arlen,

More feedback

I understood that we can keep TiddlyServer2.1 in separate folder from 
setting.json. So I think the below description may be helpful for new users

--On Windows 10


   - After testing TiddlyServer one can have a setting directory to keep 
   *setting.json*
   - The setting folder (directory) can be placed any where like 
   "C:\Users\Mohammad\Documents" (Mohammad can be another name for other user)
   - In the setting directory one can have a batch file to start the server 
   like *startServer.cmd* as below

REM TiddlyServer 2.1

node D:\TiddlyServer-2.1\server.js settings.json


   - Other folder can be in the parent folder of setting directory

Example:
 If the setting.json is locted under C:\TW\TiddlyServer2.1 then

-- C:
 TW
-- TiddlyServer
-- *setting.js*
---*startServer.cmd*
-- Personal
---Working
---Sandbox
---backups

This is while TiddlerServer itself is located in C:\Program 
Files\TiddlyServer2.1
Dont forget backups which is used to backup single file wikis

One question:

I see Tiddlyserver knows path like ~\Desktop? Does it also recognize 
absolute path?


--Mohammad



On Tuesday, December 3, 2019 at 11:30:43 PM UTC+3:30, Arlen Beiler wrote:
>
> Just thought I'd take a minute to chime in here. I made TiddlyServer to 
> solve my own problem of Massive Multi-file Online wikis. It serves the 
> folders you specify in a sort of tree allowing them to be grouped together 
> and easily navigated with the built-in directory index (even the virtual 
> directories or "groups"). When a data folder is accessed, TiddlyServer 
> automatically fires up a node instance of the TiddlyWiki listen command and 
> mounts it at that path, meaning it forwards all requests to the data folder 
> Node server instance. This makes it work identical to the TiddlyWiki listen 
> command for most normal uses of the listen command, except you can access 
> multiple data folders on the same server. Single file wikis (TW 5.1.15 and 
> newer) have a saver already built into them which TiddlyServer uses to save 
> single file wikis. Single file wikis can be backed up automatically on 
> every save, but data folders are on their own by design. I recommend 
> using Git or Dropbox for that. 
>
> There are a bunch of advanced options and even authentication, but the 
> basics are enough for most people. 
>
> It's pretty simple to use but I often notice people having trouble getting 
> it installed, so I thought I'd throw in some install instructions I wrote 
> some time ago. 
>
> It's fine to just use master (well, aka v2.1 right now) right now: 
> https://github.com/Arlen22/TiddlyServer -- Click the green "Clone or 
> Download" button then select your preferred download method. Cloning the 
> repo is an easy way to get updates but downloading is fine too. 
>
> Extract it to an empty folder so you don't risk merging with an existing 
> folder. Once you extract it you can move it wherever you want it to be. 
>
> https://nodejs.org/en/
>
> Go to NodeJS.org and download the LTS version of Node, which currently is 
> 10.x, and install it on the computer you will be running TiddlyServer on. 
> It's pretty straightforward, and the default options should work fine. 
>
> You don't actually need to install the whole thing, you can also just 
> download a zip file and extract node.exe into the TiddlyServer folder to 
> make a portable install. Since you're working with IIS I'm sure you have 
> enough computer experience know what I'm talking about, but if I'm not 
> making myself clear, just install NodeJS like I described above. 
>
> Now, here's the part that most people find tricky. Copy 
> example-settings-quick.json and name it settings.json. That's the simplest 
> setup. You can change the tree property to change what folders get served, 
> but all html files and data folders inside it should just work out of the 
> box. 
>
> The entire documentation for the settings.json file is at 
> https://arlen22.github.io/tiddlyserver/docs/serverconfig.html and the 
> tree property is the first item on the page. Here's a really simple example 
> to get you started. 
>
> "tree": {
> "myfolder": "../personal",
> "workstuff": "../work",
> "user": "~/Desktop/random",
> "projects_group": {
> "tiddlyserver": "~/Desktop/Github/TiddlyServer",
> "material-theme": "~/Dropbox/Material Theme"
> }
> }
>
>
> And that's all there is to it. Once you have your settings.json file 
> setup, just run "node server.js" to start the server. TiddlyServer expects 
> to find the settings.json file in the same directory (which is where I have 
> mine, which is why it's in .gitignore!).
>
> I made TiddlyServer simple because I want it to be simple for me to use 
> every day :) 
>
> Hope that helps 
>
> On Tue, Dec 3, 2019 at 9:02 AM Victor Dorneanu  > wrote:
>
>> Hi TT,
>>
>> it's not really related to Github. I just use to store/backup my 
>> tiddlers. The backend storage is actually quite irrelevant. I just 

Re: [tw5] Re: Best approach for multiple wikis

['Mark S.' via TiddlyWiki]

I think I need an explainer about what an "etag" is. There are etags in the 
vim editor, but I don't think you mean the same thing.

Just to repeat. Between one save and a second attempted save was more like 
6 minutes, not 6 hours. But I don't understand what the etag is and how it 
gets set.

Thanks!

On Thursday, December 5, 2019 at 12:55:52 PM UTC-8, Arlen Beiler wrote:
>
> You can disable etag checking completely if you want. If you can include 
> some more examples from the log file that would be great as well. 
>
> The relevant log file info here shows the two values, ifmatch being the 
> browser copy. The last number is the modified timestamp in milliseconds, 
> which as you can see in this case are 6 hours apart. If you google 
> "epoch converter" you can paste that into "1970 Epoch in Milliseconds" 
> converter to get the date. The third line (and similar lines in more 
> serious scenarios) are debug lines where TiddlyServer points out which 
> parts are different and caused the etag to fail. 
>
> 412 ifmatch "0-5124547-*1575414313000*"
> 412 etag "0-5124547-*1575434388000*"
> *412 caused by difference in modified*
> [2019-12-03T20:46:07.125-0800] PUT 127.0.0.1   412 127.0.0.1 
> /TW2014/T
> o.html   42.922 ms - -
>
> The docs for the putsaver.etag setting is here: 
> https://arlen22.github.io/tiddlyserver/docs/serverconfig.html#etag-string 
> 
>
> The section docs 
> https://arlen22.github.io/tiddlyserver/docs/serverconfig.html#section-putsaver
>  has 
> an example snippet. 
>
> Alternatively, you can set etagAge (which is seconds, default of 3) to a 
> ridiculously high number (like 2 hours) so it only checks the size and not 
> the timestamp. But remember that the etag is gotten when the file is 
> loaded, so even if it sits in your browser for six hours, it will still be 
> the same if the file has not been modified on disk since then. There are 
> various reasons why this could happen, which is why I added the etagAge 
> setting. Another user had the same problem and we thought it seemed like 
> the antivirus was changing the modified timestamp on certain drives for 
> some reason. 
>
> Hope that helps.
> Arlen
>
> On Wed, Dec 4, 2019 at 11:07 AM 'Mark S.' via TiddlyWiki <
> tiddl...@googlegroups.com > wrote:
>
>> Unless my computer has discovered time travel, there is no way the file 
>> on disk is 6 hours newer.
>>
>> I load.
>> I save once.
>> I do things in the TW
>> I save again ... and get the error.
>>
>> So unless the file was saved with a timestamp 6 hours in the future, it 
>> should be several minutes *older* than the browser version at the time of 
>> the save.
>>
>> I'm using 5.1.21
>>
>> I'm wondering why it checks the time at all. Unless I do something crazy 
>> like manually copy a different version to the directory, the browser 
>> version should be "king".
>>
>> Perhaps checking the date slows things down. It's noticeably slower 
>> saving a single-file wiki with TS than with BobSaver or file-backups.
>>
>> Thanks!
>>
>> On Wednesday, December 4, 2019 at 7:19:38 AM UTC-8, Arlen Beiler wrote:
>>>
>>> In this particular case, the file on disk is 6 hours newer than the copy 
>>> the browser downloaded. I have not used this feature of TiddlyServer much 
>>> so perhaps I should take a look at it again, but nothing changed since I 
>>> made it that I know of. I did run into a scenario where the etag was 
>>> changing by a second or two, so I added the putsaver.etagAge option to set 
>>> the window within which to ignore it. I will check the code to make sure 
>>> everything looks good on my end. What version of TiddlyWiki is the file?
>>>
>>> On Tue, Dec 3, 2019 at 11:53 PM 'Mark S.' via TiddlyWiki <
>>> tiddl...@googlegroups.com> wrote:
>>>
 I get "changed on server" messages regularly.  Often on the second time 
 I attempt to save. Talking single files.
 This didn't happen with the old (1.??) version. It's made it pretty 
 hard to use, since every time it happens I
 have to do a "rescue" of the changed tiddlers. If it just ignored the 
 non-existent changes on disk and saved
 it would be fine. Output below.

 412 ifmatch "0-5124547-1575414313000"
 412 etag "0-5124547-1575434388000"
 412 caused by difference in modified
 [2019-12-03T20:46:07.125-0800] PUT 127.0.0.1   412 127.0.0.1 
 /TW2014/T
 o.html   42.922 ms - -

 Thanks!

 Just thought I'd take a minute to chime in here. I made TiddlyServer to 
> solve my own problem of Massive Multi-file Online wikis. It serves the 
> folders you specify in a sort of tree allowing them to be grouped 
> together 
> and easily navigated with the built-in directory index (even the virtual 
> directories 

Re: [tw5] Re: Best approach for multiple wikis

[Arlen Beiler]

You can disable etag checking completely if you want. If you can include
some more examples from the log file that would be great as well.

The relevant log file info here shows the two values, ifmatch being the
browser copy. The last number is the modified timestamp in milliseconds,
which as you can see in this case are 6 hours apart. If you google
"epoch converter" you can paste that into "1970 Epoch in Milliseconds"
converter to get the date. The third line (and similar lines in more
serious scenarios) are debug lines where TiddlyServer points out which
parts are different and caused the etag to fail.

412 ifmatch "0-5124547-*1575414313000*"
412 etag "0-5124547-*1575434388000*"
*412 caused by difference in modified*
[2019-12-03T20:46:07.125-0800] PUT 127.0.0.1   412 127.0.0.1
/TW2014/T
o.html   42.922 ms - -

The docs for the putsaver.etag setting is here:
https://arlen22.github.io/tiddlyserver/docs/serverconfig.html#etag-string

The section docs
https://arlen22.github.io/tiddlyserver/docs/serverconfig.html#section-putsaver
has
an example snippet.

Alternatively, you can set etagAge (which is seconds, default of 3) to a
ridiculously high number (like 2 hours) so it only checks the size and not
the timestamp. But remember that the etag is gotten when the file is
loaded, so even if it sits in your browser for six hours, it will still be
the same if the file has not been modified on disk since then. There are
various reasons why this could happen, which is why I added the etagAge
setting. Another user had the same problem and we thought it seemed like
the antivirus was changing the modified timestamp on certain drives for
some reason.

Hope that helps.
Arlen

On Wed, Dec 4, 2019 at 11:07 AM 'Mark S.' via TiddlyWiki <
tiddlywiki@googlegroups.com> wrote:

> Unless my computer has discovered time travel, there is no way the file on
> disk is 6 hours newer.
>
> I load.
> I save once.
> I do things in the TW
> I save again ... and get the error.
>
> So unless the file was saved with a timestamp 6 hours in the future, it
> should be several minutes *older* than the browser version at the time of
> the save.
>
> I'm using 5.1.21
>
> I'm wondering why it checks the time at all. Unless I do something crazy
> like manually copy a different version to the directory, the browser
> version should be "king".
>
> Perhaps checking the date slows things down. It's noticeably slower saving
> a single-file wiki with TS than with BobSaver or file-backups.
>
> Thanks!
>
> On Wednesday, December 4, 2019 at 7:19:38 AM UTC-8, Arlen Beiler wrote:
>>
>> In this particular case, the file on disk is 6 hours newer than the copy
>> the browser downloaded. I have not used this feature of TiddlyServer much
>> so perhaps I should take a look at it again, but nothing changed since I
>> made it that I know of. I did run into a scenario where the etag was
>> changing by a second or two, so I added the putsaver.etagAge option to set
>> the window within which to ignore it. I will check the code to make sure
>> everything looks good on my end. What version of TiddlyWiki is the file?
>>
>> On Tue, Dec 3, 2019 at 11:53 PM 'Mark S.' via TiddlyWiki <
>> tiddl...@googlegroups.com> wrote:
>>
>>> I get "changed on server" messages regularly.  Often on the second time
>>> I attempt to save. Talking single files.
>>> This didn't happen with the old (1.??) version. It's made it pretty hard
>>> to use, since every time it happens I
>>> have to do a "rescue" of the changed tiddlers. If it just ignored the
>>> non-existent changes on disk and saved
>>> it would be fine. Output below.
>>>
>>> 412 ifmatch "0-5124547-1575414313000"
>>> 412 etag "0-5124547-1575434388000"
>>> 412 caused by difference in modified
>>> [2019-12-03T20:46:07.125-0800] PUT 127.0.0.1   412 127.0.0.1
>>> /TW2014/T
>>> o.html   42.922 ms - -
>>>
>>> Thanks!
>>>
>>> Just thought I'd take a minute to chime in here. I made TiddlyServer to
 solve my own problem of Massive Multi-file Online wikis. It serves the
 folders you specify in a sort of tree allowing them to be grouped together
 and easily navigated with the built-in directory index (even the virtual
 directories or "groups"). When a data folder is accessed, TiddlyServer
 automatically fires up a node instance of the TiddlyWiki

>>> --
>>> 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 tiddl...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/tiddlywiki/febe52b3-ed84-436d-8890-32c56bc766ef%40googlegroups.com
>>> 
>>> .
>>>
>> --
> You received this message because you are subscribed to the 

Re: [tw5] Re: Best approach for multiple wikis

['Mark S.' via TiddlyWiki]

Unless my computer has discovered time travel, there is no way the file on 
disk is 6 hours newer.

I load.
I save once.
I do things in the TW
I save again ... and get the error.

So unless the file was saved with a timestamp 6 hours in the future, it 
should be several minutes *older* than the browser version at the time of 
the save.

I'm using 5.1.21

I'm wondering why it checks the time at all. Unless I do something crazy 
like manually copy a different version to the directory, the browser 
version should be "king".

Perhaps checking the date slows things down. It's noticeably slower saving 
a single-file wiki with TS than with BobSaver or file-backups.

Thanks!

On Wednesday, December 4, 2019 at 7:19:38 AM UTC-8, Arlen Beiler wrote:
>
> In this particular case, the file on disk is 6 hours newer than the copy 
> the browser downloaded. I have not used this feature of TiddlyServer much 
> so perhaps I should take a look at it again, but nothing changed since I 
> made it that I know of. I did run into a scenario where the etag was 
> changing by a second or two, so I added the putsaver.etagAge option to set 
> the window within which to ignore it. I will check the code to make sure 
> everything looks good on my end. What version of TiddlyWiki is the file?
>
> On Tue, Dec 3, 2019 at 11:53 PM 'Mark S.' via TiddlyWiki <
> tiddl...@googlegroups.com > wrote:
>
>> I get "changed on server" messages regularly.  Often on the second time I 
>> attempt to save. Talking single files.
>> This didn't happen with the old (1.??) version. It's made it pretty hard 
>> to use, since every time it happens I
>> have to do a "rescue" of the changed tiddlers. If it just ignored the 
>> non-existent changes on disk and saved
>> it would be fine. Output below.
>>
>> 412 ifmatch "0-5124547-1575414313000"
>> 412 etag "0-5124547-1575434388000"
>> 412 caused by difference in modified
>> [2019-12-03T20:46:07.125-0800] PUT 127.0.0.1   412 127.0.0.1 
>> /TW2014/T
>> o.html   42.922 ms - -
>>
>> Thanks!
>>
>> Just thought I'd take a minute to chime in here. I made TiddlyServer to 
>>> solve my own problem of Massive Multi-file Online wikis. It serves the 
>>> folders you specify in a sort of tree allowing them to be grouped together 
>>> and easily navigated with the built-in directory index (even the virtual 
>>> directories or "groups"). When a data folder is accessed, TiddlyServer 
>>> automatically fires up a node instance of the TiddlyWiki 
>>>
>> -- 
>> 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 tiddl...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/febe52b3-ed84-436d-8890-32c56bc766ef%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/9e5321ed-ad3d-484d-97c4-f192a30c4c10%40googlegroups.com.

Re: [tw5] Re: Best approach for multiple wikis

[Arlen Beiler]

In this particular case, the file on disk is 6 hours newer than the copy
the browser downloaded. I have not used this feature of TiddlyServer much
so perhaps I should take a look at it again, but nothing changed since I
made it that I know of. I did run into a scenario where the etag was
changing by a second or two, so I added the putsaver.etagAge option to set
the window within which to ignore it. I will check the code to make sure
everything looks good on my end. What version of TiddlyWiki is the file?

On Tue, Dec 3, 2019 at 11:53 PM 'Mark S.' via TiddlyWiki <
tiddlywiki@googlegroups.com> wrote:

> I get "changed on server" messages regularly.  Often on the second time I
> attempt to save. Talking single files.
> This didn't happen with the old (1.??) version. It's made it pretty hard
> to use, since every time it happens I
> have to do a "rescue" of the changed tiddlers. If it just ignored the
> non-existent changes on disk and saved
> it would be fine. Output below.
>
> 412 ifmatch "0-5124547-1575414313000"
> 412 etag "0-5124547-1575434388000"
> 412 caused by difference in modified
> [2019-12-03T20:46:07.125-0800] PUT 127.0.0.1   412 127.0.0.1
> /TW2014/T
> o.html   42.922 ms - -
>
> Thanks!
>
> Just thought I'd take a minute to chime in here. I made TiddlyServer to
>> solve my own problem of Massive Multi-file Online wikis. It serves the
>> folders you specify in a sort of tree allowing them to be grouped together
>> and easily navigated with the built-in directory index (even the virtual
>> directories or "groups"). When a data folder is accessed, TiddlyServer
>> automatically fires up a node instance of the TiddlyWiki
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/febe52b3-ed84-436d-8890-32c56bc766ef%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSRRkb8r5nVxQA%2BBxBHZ2sSj3YcHihJGc92OPH%3DOV_Qgpg%40mail.gmail.com.

Re: [tw5] Re: Best approach for multiple wikis

[Victor Dorneanu]

Wow! This is (almost) exactly what I was looking for. Thanks for sharing 
and for your efforts bringing down your ideas and concepts to code. 

I'll definitely give it a try. 

Cheers, 
Victor 

On Tuesday, December 3, 2019 at 9:00:43 PM UTC+1, Arlen Beiler wrote:
>
> Just thought I'd take a minute to chime in here. I made TiddlyServer to 
> solve my own problem of Massive Multi-file Online wikis. It serves the 
> folders you specify in a sort of tree allowing them to be grouped together 
> and easily navigated with the built-in directory index (even the virtual 
> directories or "groups"). When a data folder is accessed, TiddlyServer 
> automatically fires up a node instance of the TiddlyWiki listen command and 
> mounts it at that path, meaning it forwards all requests to the data folder 
> Node server instance. This makes it work identical to the TiddlyWiki listen 
> command for most normal uses of the listen command, except you can access 
> multiple data folders on the same server. Single file wikis (TW 5.1.15 and 
> newer) have a saver already built into them which TiddlyServer uses to save 
> single file wikis. Single file wikis can be backed up automatically on 
> every save, but data folders are on their own by design. I recommend 
> using Git or Dropbox for that. 
>
> There are a bunch of advanced options and even authentication, but the 
> basics are enough for most people. 
>
> It's pretty simple to use but I often notice people having trouble getting 
> it installed, so I thought I'd throw in some install instructions I wrote 
> some time ago. 
>
> It's fine to just use master (well, aka v2.1 right now) right now: 
> https://github.com/Arlen22/TiddlyServer -- Click the green "Clone or 
> Download" button then select your preferred download method. Cloning the 
> repo is an easy way to get updates but downloading is fine too. 
>
> Extract it to an empty folder so you don't risk merging with an existing 
> folder. Once you extract it you can move it wherever you want it to be. 
>
> https://nodejs.org/en/
>
> Go to NodeJS.org and download the LTS version of Node, which currently is 
> 10.x, and install it on the computer you will be running TiddlyServer on. 
> It's pretty straightforward, and the default options should work fine. 
>
> You don't actually need to install the whole thing, you can also just 
> download a zip file and extract node.exe into the TiddlyServer folder to 
> make a portable install. Since you're working with IIS I'm sure you have 
> enough computer experience know what I'm talking about, but if I'm not 
> making myself clear, just install NodeJS like I described above. 
>
> Now, here's the part that most people find tricky. Copy 
> example-settings-quick.json and name it settings.json. That's the simplest 
> setup. You can change the tree property to change what folders get served, 
> but all html files and data folders inside it should just work out of the 
> box. 
>
> The entire documentation for the settings.json file is at 
> https://arlen22.github.io/tiddlyserver/docs/serverconfig.html and the 
> tree property is the first item on the page. Here's a really simple example 
> to get you started. 
>
> "tree": {
> "myfolder": "../personal",
> "workstuff": "../work",
> "user": "~/Desktop/random",
> "projects_group": {
> "tiddlyserver": "~/Desktop/Github/TiddlyServer",
> "material-theme": "~/Dropbox/Material Theme"
> }
> }
>
>
> And that's all there is to it. Once you have your settings.json file 
> setup, just run "node server.js" to start the server. TiddlyServer expects 
> to find the settings.json file in the same directory (which is where I have 
> mine, which is why it's in .gitignore!).
>
> I made TiddlyServer simple because I want it to be simple for me to use 
> every day :) 
>
> Hope that helps 
>
> On Tue, Dec 3, 2019 at 9:02 AM Victor Dorneanu  > wrote:
>
>> Hi TT,
>>
>> it's not really related to Github. I just use to store/backup my 
>> tiddlers. The backend storage is actually quite irrelevant. I just need 
>> some "best practices" / workflows that individuals have established over 
>> time in order to manage multiple wikis. 
>>
>> Cheers, 
>> Victor
>>
>> On Tuesday, December 3, 2019 at 12:26:32 PM UTC+1, TiddlyTweeter wrote:
>>>
>>> Ciao Victor
>>>
>>> As far as I understand GitHub it can be used (with various sub-tools) to 
>>> create workflows of complexity & sophistication.
>>>
>>> I don't have the knowledge to advise on particulars. 
>>>
>>> But I think this may be more a question for asking on GitHub itself?
>>>
>>> Best wishes
>>> TT
>>>
>>> On Monday, 2 December 2019 11:39:56 UTC+1, Victor Dorneanu wrote:

 Hi everyone, 

 what I want to achieve is to have multiple wikis for each "area" of 
 knowledge. Let's say:


- coding
- notes (from books, articles etc.)
- cooking recipes
- etc.


 I like to manage my tiddlers at a single place, that means: Have 
 everything inside a big 

Re: [tw5] Re: Best approach for multiple wikis

['Mark S.' via TiddlyWiki]

It only happens with TiddlyServer -- not BobSaver or file-backups. Often I 
don't even leave the tab.  It's falsely detecting a change on the disk. But 
I don't understand why it's even checking for a change. Perhaps it was/is 
useful with data folders.

On Tuesday, December 3, 2019 at 9:10:40 PM UTC-8, TonyM wrote:
>
> Mark
>
> I think the issue is if you return to a wiki in a tab after a while, even 
> a browser or pc reboot to a wiki that has not being reloaded before you 
> made changes causes this.
>
> Perhaps there is a fix, but an emergency export changes only, reload, 
> import changes in the work around.
>
> Eventualy I will publish a set of custom save buttons for this situation.
>
> Tony 
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/98878265-75d0-4505-ade3-a4fb39b2633f%40googlegroups.com.

Re: [tw5] Re: Best approach for multiple wikis

[TonyM]

Mark

I think the issue is if you return to a wiki in a tab after a while, even a 
browser or pc reboot to a wiki that has not being reloaded before you made 
changes causes this.

Perhaps there is a fix, but an emergency export changes only, reload, import 
changes in the work around.

Eventualy I will publish a set of custom save buttons for this situation.

Tony 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/9fa557fe-d9d6-487c-ad5a-fa3bc96f79a1%40googlegroups.com.

Re: [tw5] Re: Best approach for multiple wikis

['Mark S.' via TiddlyWiki]

I get "changed on server" messages regularly.  Often on the second time I 
attempt to save. Talking single files.
This didn't happen with the old (1.??) version. It's made it pretty hard to 
use, since every time it happens I
have to do a "rescue" of the changed tiddlers. If it just ignored the 
non-existent changes on disk and saved
it would be fine. Output below.

412 ifmatch "0-5124547-1575414313000"
412 etag "0-5124547-1575434388000"
412 caused by difference in modified
[2019-12-03T20:46:07.125-0800] PUT 127.0.0.1   412 127.0.0.1 
/TW2014/T
o.html   42.922 ms - -

Thanks!

Just thought I'd take a minute to chime in here. I made TiddlyServer to 
> solve my own problem of Massive Multi-file Online wikis. It serves the 
> folders you specify in a sort of tree allowing them to be grouped together 
> and easily navigated with the built-in directory index (even the virtual 
> directories or "groups"). When a data folder is accessed, TiddlyServer 
> automatically fires up a node instance of the TiddlyWiki 
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/febe52b3-ed84-436d-8890-32c56bc766ef%40googlegroups.com.

Re: [tw5] Re: Best approach for multiple wikis

[TonyM]

On the beautification process, of TiddlyServer

Could there be a html template that can be crafted as an alternative?

One could then publish host information, Links to key resources, guidelines 
of use etc... on arriving at the server!

Regards
Tony

On Wednesday, December 4, 2019 at 10:11:44 AM UTC+11, Mohammad wrote:
>
> Many thanks Arlen!
>
> TiddlyServer is really amazing and lets work with multiple wiki out of the 
> box!
> I may send further comments later after I evaluate it with some experiment!
>
> Yes, other people should read documents an send their feedback how they 
> get things working by following the tutorial!
> My feedback was just what I encountered by reading tutorial here 
> https://arlen22.github.io/tiddlyserver/docs/serverconfig.html and
> your description in above post.
>
> Just a minor comment:
>  I think like TiddlyDesktop it is possible to customize and beatify the 
> landing page and  folder pages of TiddlyServer. May be you can use 
> Tiddlywiki itself for this purpose!
>
> --Mohammad
>
> On Wednesday, December 4, 2019 at 1:53:33 AM UTC+3:30, Arlen Beiler wrote:
>>
>> You can set "_datafoldertarget": "../some/path" in settings.json to any 
>> TiddlyWiki folder you want. Relative paths are relative to the 
>> settings.json file. You can see it in the example in 
>> https://arlen22.github.io/tiddlyserver/docs/serverconfig.html although I 
>> don't mention it anywhere on that page. Thank you for your feedback. I'll 
>> try to update my docs to make it more clear.
>>
>> On Tue, Dec 3, 2019 at 5:08 PM Mohammad  wrote:
>>
>>> Arlen,
>>>  Is it possible to use 5.1.22p or other version of TW instead of the 
>>> preconfigured 5.21?
>>>
>>> --Mohammad
>>>
>>> -- 
>>> 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 tiddl...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/tiddlywiki/66f697ef-cc1c-4a53-8ebe-f7cd7bd924d5%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/dba1d2b6-9ae1-4ed2-8828-70c402c8d6f4%40googlegroups.com.

Re: [tw5] Re: Best approach for multiple wikis

[Mohammad]

Many thanks Arlen!

TiddlyServer is really amazing and lets work with multiple wiki out of the 
box!
I may send further comments later after I evaluate it with some experiment!

Yes, other people should read documents an send their feedback how they get 
things working by following the tutorial!
My feedback was just what I encountered by reading tutorial here 
https://arlen22.github.io/tiddlyserver/docs/serverconfig.html and
your description in above post.

Just a minor comment:
 I think like TiddlyDesktop it is possible to customize and beatify the 
landing page and  folder pages of TiddlyServer. May be you can use 
Tiddlywiki itself for this purpose!

--Mohammad

On Wednesday, December 4, 2019 at 1:53:33 AM UTC+3:30, Arlen Beiler wrote:
>
> You can set "_datafoldertarget": "../some/path" in settings.json to any 
> TiddlyWiki folder you want. Relative paths are relative to the 
> settings.json file. You can see it in the example in 
> https://arlen22.github.io/tiddlyserver/docs/serverconfig.html although I 
> don't mention it anywhere on that page. Thank you for your feedback. I'll 
> try to update my docs to make it more clear.
>
> On Tue, Dec 3, 2019 at 5:08 PM Mohammad  > wrote:
>
>> Arlen,
>>  Is it possible to use 5.1.22p or other version of TW instead of the 
>> preconfigured 5.21?
>>
>> --Mohammad
>>
>> -- 
>> 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 tiddl...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/66f697ef-cc1c-4a53-8ebe-f7cd7bd924d5%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/40803170-66df-4e1a-98cb-35a8da78caad%40googlegroups.com.

Re: [tw5] Re: Best approach for multiple wikis

[Arlen Beiler]

You can set "_datafoldertarget": "../some/path" in settings.json to any
TiddlyWiki folder you want. Relative paths are relative to the
settings.json file. You can see it in the example in
https://arlen22.github.io/tiddlyserver/docs/serverconfig.html although I
don't mention it anywhere on that page. Thank you for your feedback. I'll
try to update my docs to make it more clear.

On Tue, Dec 3, 2019 at 5:08 PM Mohammad  wrote:

> Arlen,
>  Is it possible to use 5.1.22p or other version of TW instead of the
> preconfigured 5.21?
>
> --Mohammad
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/66f697ef-cc1c-4a53-8ebe-f7cd7bd924d5%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSTUCJT-4YbRDVaP_rkHRunW3Dt0i2FMq0bxWJZ5h1nD9w%40mail.gmail.com.

Re: [tw5] Re: Best approach for multiple wikis

[Mohammad]

Arlen,
 Is it possible to use 5.1.22p or other version of TW instead of the 
preconfigured 5.21?

--Mohammad

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/66f697ef-cc1c-4a53-8ebe-f7cd7bd924d5%40googlegroups.com.

Re: [tw5] Re: Best approach for multiple wikis

[Mohammad]

Arlen, The error 500 was because there was no ../backups folder!
I did not see this in tutorial nor quick startup!

Many thanks now I have runing TiddlyServer 2.1 on Windows 10 + Node.js 12.3


Note:
 The LTS version of Node.js is 12.13.1

Cheers
Mohammad

On Wednesday, December 4, 2019 at 12:10:29 AM UTC+3:30, Arlen Beiler wrote:
>
> You can put your single file wikis, data folders, and other files in 
> there. Then you open your browser and navigate to the particular folder or 
> item you want. 
>
> On Tue, Dec 3, 2019 at 3:36 PM Mohammad  > wrote:
>
>> Arlen,
>>  I followed all these instruction and everything work well! but then
>> what should be in folders for example personal folder!
>> It does not seem TiddlyServer create a wiki there
>>
>> --Mohammad
>>
>> On Tuesday, December 3, 2019 at 11:30:43 PM UTC+3:30, Arlen Beiler wrote:
>>>
>>> Just thought I'd take a minute to chime in here. I made TiddlyServer to 
>>> solve my own problem of Massive Multi-file Online wikis. It serves the 
>>> folders you specify in a sort of tree allowing them to be grouped together 
>>> and easily navigated with the built-in directory index (even the virtual 
>>> directories or "groups"). When a data folder is accessed, TiddlyServer 
>>> automatically fires up a node instance of the TiddlyWiki listen command and 
>>> mounts it at that path, meaning it forwards all requests to the data folder 
>>> Node server instance. This makes it work identical to the TiddlyWiki listen 
>>> command for most normal uses of the listen command, except you can access 
>>> multiple data folders on the same server. Single file wikis (TW 5.1.15 and 
>>> newer) have a saver already built into them which TiddlyServer uses to save 
>>> single file wikis. Single file wikis can be backed up automatically on 
>>> every save, but data folders are on their own by design. I recommend 
>>> using Git or Dropbox for that. 
>>>
>>> There are a bunch of advanced options and even authentication, but the 
>>> basics are enough for most people. 
>>>
>>> It's pretty simple to use but I often notice people having trouble 
>>> getting it installed, so I thought I'd throw in some install instructions I 
>>> wrote some time ago. 
>>>
>>> It's fine to just use master (well, aka v2.1 right now) right now: 
>>> https://github.com/Arlen22/TiddlyServer -- Click the green "Clone or 
>>> Download" button then select your preferred download method. Cloning the 
>>> repo is an easy way to get updates but downloading is fine too. 
>>>
>>> Extract it to an empty folder so you don't risk merging with an existing 
>>> folder. Once you extract it you can move it wherever you want it to be. 
>>>
>>> https://nodejs.org/en/
>>>
>>> Go to NodeJS.org and download the LTS version of Node, which currently 
>>> is 10.x, and install it on the computer you will be running TiddlyServer 
>>> on. It's pretty straightforward, and the default options should work fine. 
>>>
>>> You don't actually need to install the whole thing, you can also just 
>>> download a zip file and extract node.exe into the TiddlyServer folder to 
>>> make a portable install. Since you're working with IIS I'm sure you have 
>>> enough computer experience know what I'm talking about, but if I'm not 
>>> making myself clear, just install NodeJS like I described above. 
>>>
>>> Now, here's the part that most people find tricky. Copy 
>>> example-settings-quick.json and name it settings.json. That's the simplest 
>>> setup. You can change the tree property to change what folders get served, 
>>> but all html files and data folders inside it should just work out of the 
>>> box. 
>>>
>>> The entire documentation for the settings.json file is at 
>>> https://arlen22.github.io/tiddlyserver/docs/serverconfig.html and the 
>>> tree property is the first item on the page. Here's a really simple example 
>>> to get you started. 
>>>
>>> "tree": {
>>> "myfolder": "../personal",
>>> "workstuff": "../work",
>>> "user": "~/Desktop/random",
>>> "projects_group": {
>>> "tiddlyserver": "~/Desktop/Github/TiddlyServer",
>>> "material-theme": "~/Dropbox/Material Theme"
>>> }
>>> }
>>>
>>>
>>> And that's all there is to it. Once you have your settings.json file 
>>> setup, just run "node server.js" to start the server. TiddlyServer expects 
>>> to find the settings.json file in the same directory (which is where I have 
>>> mine, which is why it's in .gitignore!).
>>>
>>> I made TiddlyServer simple because I want it to be simple for me to use 
>>> every day :) 
>>>
>>> Hope that helps 
>>>
>>> On Tue, Dec 3, 2019 at 9:02 AM Victor Dorneanu  wrote:
>>>
 Hi TT,

 it's not really related to Github. I just use to store/backup my 
 tiddlers. The backend storage is actually quite irrelevant. I just need 
 some "best practices" / workflows that individuals have established over 
 time in order to manage multiple wikis. 

 Cheers, 
 Victor

 On Tuesday, December 3, 2019 at 12:26:32 PM UTC+1, 

Re: [tw5] Re: Best approach for multiple wikis

[Mohammad]

Arlen, I understood empty folder on click open a new page and lets upload a 
single wiki file or create data folder
Than you I can run the wiki in data folder but still unsuccessful on single 
wiki!

These steps are not explained in tutorial nor in quick startup!

Just feedback as a newbie!

--Mohammad

On Wednesday, December 4, 2019 at 12:10:29 AM UTC+3:30, Arlen Beiler wrote:
>
> You can put your single file wikis, data folders, and other files in 
> there. Then you open your browser and navigate to the particular folder or 
> item you want. 
>
> On Tue, Dec 3, 2019 at 3:36 PM Mohammad  > wrote:
>
>> Arlen,
>>  I followed all these instruction and everything work well! but then
>> what should be in folders for example personal folder!
>> It does not seem TiddlyServer create a wiki there
>>
>> --Mohammad
>>
>> On Tuesday, December 3, 2019 at 11:30:43 PM UTC+3:30, Arlen Beiler wrote:
>>>
>>> Just thought I'd take a minute to chime in here. I made TiddlyServer to 
>>> solve my own problem of Massive Multi-file Online wikis. It serves the 
>>> folders you specify in a sort of tree allowing them to be grouped together 
>>> and easily navigated with the built-in directory index (even the virtual 
>>> directories or "groups"). When a data folder is accessed, TiddlyServer 
>>> automatically fires up a node instance of the TiddlyWiki listen command and 
>>> mounts it at that path, meaning it forwards all requests to the data folder 
>>> Node server instance. This makes it work identical to the TiddlyWiki listen 
>>> command for most normal uses of the listen command, except you can access 
>>> multiple data folders on the same server. Single file wikis (TW 5.1.15 and 
>>> newer) have a saver already built into them which TiddlyServer uses to save 
>>> single file wikis. Single file wikis can be backed up automatically on 
>>> every save, but data folders are on their own by design. I recommend 
>>> using Git or Dropbox for that. 
>>>
>>> There are a bunch of advanced options and even authentication, but the 
>>> basics are enough for most people. 
>>>
>>> It's pretty simple to use but I often notice people having trouble 
>>> getting it installed, so I thought I'd throw in some install instructions I 
>>> wrote some time ago. 
>>>
>>> It's fine to just use master (well, aka v2.1 right now) right now: 
>>> https://github.com/Arlen22/TiddlyServer -- Click the green "Clone or 
>>> Download" button then select your preferred download method. Cloning the 
>>> repo is an easy way to get updates but downloading is fine too. 
>>>
>>> Extract it to an empty folder so you don't risk merging with an existing 
>>> folder. Once you extract it you can move it wherever you want it to be. 
>>>
>>> https://nodejs.org/en/
>>>
>>> Go to NodeJS.org and download the LTS version of Node, which currently 
>>> is 10.x, and install it on the computer you will be running TiddlyServer 
>>> on. It's pretty straightforward, and the default options should work fine. 
>>>
>>> You don't actually need to install the whole thing, you can also just 
>>> download a zip file and extract node.exe into the TiddlyServer folder to 
>>> make a portable install. Since you're working with IIS I'm sure you have 
>>> enough computer experience know what I'm talking about, but if I'm not 
>>> making myself clear, just install NodeJS like I described above. 
>>>
>>> Now, here's the part that most people find tricky. Copy 
>>> example-settings-quick.json and name it settings.json. That's the simplest 
>>> setup. You can change the tree property to change what folders get served, 
>>> but all html files and data folders inside it should just work out of the 
>>> box. 
>>>
>>> The entire documentation for the settings.json file is at 
>>> https://arlen22.github.io/tiddlyserver/docs/serverconfig.html and the 
>>> tree property is the first item on the page. Here's a really simple example 
>>> to get you started. 
>>>
>>> "tree": {
>>> "myfolder": "../personal",
>>> "workstuff": "../work",
>>> "user": "~/Desktop/random",
>>> "projects_group": {
>>> "tiddlyserver": "~/Desktop/Github/TiddlyServer",
>>> "material-theme": "~/Dropbox/Material Theme"
>>> }
>>> }
>>>
>>>
>>> And that's all there is to it. Once you have your settings.json file 
>>> setup, just run "node server.js" to start the server. TiddlyServer expects 
>>> to find the settings.json file in the same directory (which is where I have 
>>> mine, which is why it's in .gitignore!).
>>>
>>> I made TiddlyServer simple because I want it to be simple for me to use 
>>> every day :) 
>>>
>>> Hope that helps 
>>>
>>> On Tue, Dec 3, 2019 at 9:02 AM Victor Dorneanu  wrote:
>>>
 Hi TT,

 it's not really related to Github. I just use to store/backup my 
 tiddlers. The backend storage is actually quite irrelevant. I just need 
 some "best practices" / workflows that individuals have established over 
 time in order to manage multiple wikis. 

 Cheers, 
 Victor

 On Tuesday, 

Re: [tw5] Re: Best approach for multiple wikis

[Mohammad]

Thanks Arlen

1. In the tutorial there is no description about what this so please add 
this to tutorial
2. I add a data folder and it works
3. I also put a single file wiki in personal but on save it raises an 
error: XMLHttpRequest Error 500


--Mohammad

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/c9cb47c8-4e06-4f86-9ecb-5786419e60ca%40googlegroups.com.

Re: [tw5] Re: Best approach for multiple wikis

[Arlen Beiler]

You can put your single file wikis, data folders, and other files in there.
Then you open your browser and navigate to the particular folder or item
you want.

On Tue, Dec 3, 2019 at 3:36 PM Mohammad  wrote:

> Arlen,
>  I followed all these instruction and everything work well! but then
> what should be in folders for example personal folder!
> It does not seem TiddlyServer create a wiki there
>
> --Mohammad
>
> On Tuesday, December 3, 2019 at 11:30:43 PM UTC+3:30, Arlen Beiler wrote:
>>
>> Just thought I'd take a minute to chime in here. I made TiddlyServer to
>> solve my own problem of Massive Multi-file Online wikis. It serves the
>> folders you specify in a sort of tree allowing them to be grouped together
>> and easily navigated with the built-in directory index (even the virtual
>> directories or "groups"). When a data folder is accessed, TiddlyServer
>> automatically fires up a node instance of the TiddlyWiki listen command and
>> mounts it at that path, meaning it forwards all requests to the data folder
>> Node server instance. This makes it work identical to the TiddlyWiki listen
>> command for most normal uses of the listen command, except you can access
>> multiple data folders on the same server. Single file wikis (TW 5.1.15 and
>> newer) have a saver already built into them which TiddlyServer uses to save
>> single file wikis. Single file wikis can be backed up automatically on
>> every save, but data folders are on their own by design. I recommend
>> using Git or Dropbox for that.
>>
>> There are a bunch of advanced options and even authentication, but the
>> basics are enough for most people.
>>
>> It's pretty simple to use but I often notice people having trouble
>> getting it installed, so I thought I'd throw in some install instructions I
>> wrote some time ago.
>>
>> It's fine to just use master (well, aka v2.1 right now) right now:
>> https://github.com/Arlen22/TiddlyServer -- Click the green "Clone or
>> Download" button then select your preferred download method. Cloning the
>> repo is an easy way to get updates but downloading is fine too.
>>
>> Extract it to an empty folder so you don't risk merging with an existing
>> folder. Once you extract it you can move it wherever you want it to be.
>>
>> https://nodejs.org/en/
>>
>> Go to NodeJS.org and download the LTS version of Node, which currently is
>> 10.x, and install it on the computer you will be running TiddlyServer on.
>> It's pretty straightforward, and the default options should work fine.
>>
>> You don't actually need to install the whole thing, you can also just
>> download a zip file and extract node.exe into the TiddlyServer folder to
>> make a portable install. Since you're working with IIS I'm sure you have
>> enough computer experience know what I'm talking about, but if I'm not
>> making myself clear, just install NodeJS like I described above.
>>
>> Now, here's the part that most people find tricky. Copy
>> example-settings-quick.json and name it settings.json. That's the simplest
>> setup. You can change the tree property to change what folders get served,
>> but all html files and data folders inside it should just work out of the
>> box.
>>
>> The entire documentation for the settings.json file is at
>> https://arlen22.github.io/tiddlyserver/docs/serverconfig.html and the
>> tree property is the first item on the page. Here's a really simple example
>> to get you started.
>>
>> "tree": {
>> "myfolder": "../personal",
>> "workstuff": "../work",
>> "user": "~/Desktop/random",
>> "projects_group": {
>> "tiddlyserver": "~/Desktop/Github/TiddlyServer",
>> "material-theme": "~/Dropbox/Material Theme"
>> }
>> }
>>
>>
>> And that's all there is to it. Once you have your settings.json file
>> setup, just run "node server.js" to start the server. TiddlyServer expects
>> to find the settings.json file in the same directory (which is where I have
>> mine, which is why it's in .gitignore!).
>>
>> I made TiddlyServer simple because I want it to be simple for me to use
>> every day :)
>>
>> Hope that helps
>>
>> On Tue, Dec 3, 2019 at 9:02 AM Victor Dorneanu  wrote:
>>
>>> Hi TT,
>>>
>>> it's not really related to Github. I just use to store/backup my
>>> tiddlers. The backend storage is actually quite irrelevant. I just need
>>> some "best practices" / workflows that individuals have established over
>>> time in order to manage multiple wikis.
>>>
>>> Cheers,
>>> Victor
>>>
>>> On Tuesday, December 3, 2019 at 12:26:32 PM UTC+1, TiddlyTweeter wrote:

 Ciao Victor

 As far as I understand GitHub it can be used (with various sub-tools)
 to create workflows of complexity & sophistication.

 I don't have the knowledge to advise on particulars.

 But I think this may be more a question for asking on GitHub itself?

 Best wishes
 TT

 On Monday, 2 December 2019 11:39:56 UTC+1, Victor Dorneanu wrote:
>
> Hi everyone,
>
> what I want to achieve is to have multiple 

Re: [tw5] Re: Best approach for multiple wikis

[Mohammad]

Arlen,
 I followed all these instruction and everything work well! but then
what should be in folders for example personal folder!
It does not seem TiddlyServer create a wiki there

--Mohammad

On Tuesday, December 3, 2019 at 11:30:43 PM UTC+3:30, Arlen Beiler wrote:
>
> Just thought I'd take a minute to chime in here. I made TiddlyServer to 
> solve my own problem of Massive Multi-file Online wikis. It serves the 
> folders you specify in a sort of tree allowing them to be grouped together 
> and easily navigated with the built-in directory index (even the virtual 
> directories or "groups"). When a data folder is accessed, TiddlyServer 
> automatically fires up a node instance of the TiddlyWiki listen command and 
> mounts it at that path, meaning it forwards all requests to the data folder 
> Node server instance. This makes it work identical to the TiddlyWiki listen 
> command for most normal uses of the listen command, except you can access 
> multiple data folders on the same server. Single file wikis (TW 5.1.15 and 
> newer) have a saver already built into them which TiddlyServer uses to save 
> single file wikis. Single file wikis can be backed up automatically on 
> every save, but data folders are on their own by design. I recommend 
> using Git or Dropbox for that. 
>
> There are a bunch of advanced options and even authentication, but the 
> basics are enough for most people. 
>
> It's pretty simple to use but I often notice people having trouble getting 
> it installed, so I thought I'd throw in some install instructions I wrote 
> some time ago. 
>
> It's fine to just use master (well, aka v2.1 right now) right now: 
> https://github.com/Arlen22/TiddlyServer -- Click the green "Clone or 
> Download" button then select your preferred download method. Cloning the 
> repo is an easy way to get updates but downloading is fine too. 
>
> Extract it to an empty folder so you don't risk merging with an existing 
> folder. Once you extract it you can move it wherever you want it to be. 
>
> https://nodejs.org/en/
>
> Go to NodeJS.org and download the LTS version of Node, which currently is 
> 10.x, and install it on the computer you will be running TiddlyServer on. 
> It's pretty straightforward, and the default options should work fine. 
>
> You don't actually need to install the whole thing, you can also just 
> download a zip file and extract node.exe into the TiddlyServer folder to 
> make a portable install. Since you're working with IIS I'm sure you have 
> enough computer experience know what I'm talking about, but if I'm not 
> making myself clear, just install NodeJS like I described above. 
>
> Now, here's the part that most people find tricky. Copy 
> example-settings-quick.json and name it settings.json. That's the simplest 
> setup. You can change the tree property to change what folders get served, 
> but all html files and data folders inside it should just work out of the 
> box. 
>
> The entire documentation for the settings.json file is at 
> https://arlen22.github.io/tiddlyserver/docs/serverconfig.html and the 
> tree property is the first item on the page. Here's a really simple example 
> to get you started. 
>
> "tree": {
> "myfolder": "../personal",
> "workstuff": "../work",
> "user": "~/Desktop/random",
> "projects_group": {
> "tiddlyserver": "~/Desktop/Github/TiddlyServer",
> "material-theme": "~/Dropbox/Material Theme"
> }
> }
>
>
> And that's all there is to it. Once you have your settings.json file 
> setup, just run "node server.js" to start the server. TiddlyServer expects 
> to find the settings.json file in the same directory (which is where I have 
> mine, which is why it's in .gitignore!).
>
> I made TiddlyServer simple because I want it to be simple for me to use 
> every day :) 
>
> Hope that helps 
>
> On Tue, Dec 3, 2019 at 9:02 AM Victor Dorneanu  > wrote:
>
>> Hi TT,
>>
>> it's not really related to Github. I just use to store/backup my 
>> tiddlers. The backend storage is actually quite irrelevant. I just need 
>> some "best practices" / workflows that individuals have established over 
>> time in order to manage multiple wikis. 
>>
>> Cheers, 
>> Victor
>>
>> On Tuesday, December 3, 2019 at 12:26:32 PM UTC+1, TiddlyTweeter wrote:
>>>
>>> Ciao Victor
>>>
>>> As far as I understand GitHub it can be used (with various sub-tools) to 
>>> create workflows of complexity & sophistication.
>>>
>>> I don't have the knowledge to advise on particulars. 
>>>
>>> But I think this may be more a question for asking on GitHub itself?
>>>
>>> Best wishes
>>> TT
>>>
>>> On Monday, 2 December 2019 11:39:56 UTC+1, Victor Dorneanu wrote:

 Hi everyone, 

 what I want to achieve is to have multiple wikis for each "area" of 
 knowledge. Let's say:


- coding
- notes (from books, articles etc.)
- cooking recipes
- etc.


 I like to manage my tiddlers at a single place, that means: Have 
 everything inside a 

Re: [tw5] Re: Best approach for multiple wikis

[Arlen Beiler]

Just thought I'd take a minute to chime in here. I made TiddlyServer to
solve my own problem of Massive Multi-file Online wikis. It serves the
folders you specify in a sort of tree allowing them to be grouped together
and easily navigated with the built-in directory index (even the virtual
directories or "groups"). When a data folder is accessed, TiddlyServer
automatically fires up a node instance of the TiddlyWiki listen command and
mounts it at that path, meaning it forwards all requests to the data folder
Node server instance. This makes it work identical to the TiddlyWiki listen
command for most normal uses of the listen command, except you can access
multiple data folders on the same server. Single file wikis (TW 5.1.15 and
newer) have a saver already built into them which TiddlyServer uses to save
single file wikis. Single file wikis can be backed up automatically on
every save, but data folders are on their own by design. I recommend using
Git or Dropbox for that.

There are a bunch of advanced options and even authentication, but the
basics are enough for most people.

It's pretty simple to use but I often notice people having trouble getting
it installed, so I thought I'd throw in some install instructions I wrote
some time ago.

It's fine to just use master (well, aka v2.1 right now) right now:
https://github.com/Arlen22/TiddlyServer -- Click the green "Clone or
Download" button then select your preferred download method. Cloning the
repo is an easy way to get updates but downloading is fine too.

Extract it to an empty folder so you don't risk merging with an existing
folder. Once you extract it you can move it wherever you want it to be.

https://nodejs.org/en/

Go to NodeJS.org and download the LTS version of Node, which currently is
10.x, and install it on the computer you will be running TiddlyServer on.
It's pretty straightforward, and the default options should work fine.

You don't actually need to install the whole thing, you can also just
download a zip file and extract node.exe into the TiddlyServer folder to
make a portable install. Since you're working with IIS I'm sure you have
enough computer experience know what I'm talking about, but if I'm not
making myself clear, just install NodeJS like I described above.

Now, here's the part that most people find tricky. Copy
example-settings-quick.json and name it settings.json. That's the simplest
setup. You can change the tree property to change what folders get served,
but all html files and data folders inside it should just work out of the
box.

The entire documentation for the settings.json file is at
https://arlen22.github.io/tiddlyserver/docs/serverconfig.html and the tree
property is the first item on the page. Here's a really simple example to
get you started.

"tree": {
"myfolder": "../personal",
"workstuff": "../work",
"user": "~/Desktop/random",
"projects_group": {
"tiddlyserver": "~/Desktop/Github/TiddlyServer",
"material-theme": "~/Dropbox/Material Theme"
}
}


And that's all there is to it. Once you have your settings.json file setup,
just run "node server.js" to start the server. TiddlyServer expects to find
the settings.json file in the same directory (which is where I have mine,
which is why it's in .gitignore!).

I made TiddlyServer simple because I want it to be simple for me to use
every day :)

Hope that helps

On Tue, Dec 3, 2019 at 9:02 AM Victor Dorneanu  wrote:

> Hi TT,
>
> it's not really related to Github. I just use to store/backup my tiddlers.
> The backend storage is actually quite irrelevant. I just need some "best
> practices" / workflows that individuals have established over time in order
> to manage multiple wikis.
>
> Cheers,
> Victor
>
> On Tuesday, December 3, 2019 at 12:26:32 PM UTC+1, TiddlyTweeter wrote:
>>
>> Ciao Victor
>>
>> As far as I understand GitHub it can be used (with various sub-tools) to
>> create workflows of complexity & sophistication.
>>
>> I don't have the knowledge to advise on particulars.
>>
>> But I think this may be more a question for asking on GitHub itself?
>>
>> Best wishes
>> TT
>>
>> On Monday, 2 December 2019 11:39:56 UTC+1, Victor Dorneanu wrote:
>>>
>>> Hi everyone,
>>>
>>> what I want to achieve is to have multiple wikis for each "area" of
>>> knowledge. Let's say:
>>>
>>>
>>>- coding
>>>- notes (from books, articles etc.)
>>>- cooking recipes
>>>- etc.
>>>
>>>
>>> I like to manage my tiddlers at a single place, that means: Have
>>> everything inside a big (git) repository. However, when I want to
>>> share/publish my content I'd like to have multiple files for each knowledge
>>> area:
>>>
>>>
>>>- coding.html (for coding)
>>>   - everything that is tagged with "coding" or has "coding" as a
>>>   parent tag
>>>   - notes.html (for notes)
>>>   - everything that is tagged with "notes" or has "notes" as a
>>>   parent tag
>>>- and so forth
>>>
>>>
>>> For every published wiki I'd like to also have a different welcome page