[tw] Re: ThirdFlow throwing dozens of errors
Alright, just tested. Actually this works shockingly well, better than I would have hoped. Process below: - Backup the TW as .html (simpler to wield than a potentially huge amount of individual tiddler files). - Create a new server instance (http://tiddlywiki.com/static/Installing%2520TiddlyWiki%2520on%2520Node.js.html using these instructions). - Import your $:/config/FileSystemPaths tiddler by dragging the .html backup in that instance and unticking everything but that tiddler. - Then, import the remainder of your .html backup by repeating the above step and ticking everything instead. (This is to make sure $:/config/FileSystemPaths is live by the time everything else gets imported). Most likely you'll want to overwrite everything when there's a conflict (assuming your backup had up-to-date code). Because backing up the TW as .html ignores folder structure, this process can probably be repeated ad infinitum (i.e. you can change your folder logic in $:/config/FileSystemPaths and then repeat the process as often as you'd like, incrementally remodeling your TW server into the shape of your desires). Thanks a lot for the tip! This solved my problem, and them some. kodomohimari On Tuesday, September 19, 2017 at 9:51:28 AM UTC+2, PMario wrote: > > On Monday, September 18, 2017 at 11:45:13 PM UTC+2, kodomohimari wrote: >> >> Ah, I actually saw that one earlier but I haven't been able to find a way >> to apply it retroactively... >> > > Not really. The settings work for new tiddlers only. but > > >> Is there any way for this method to dynamically re-check every tiddler in >> the TW instance and rename whatever deserves renaming? >> > > - You can create an empty TW > - Change the settings in a way that work for your > - Drag and drop import an existing TW. > - Importing should treat every tiddler as a new one, ... > > That's the only way I can think of. ... but I didn't test it. > > -m > > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/5c338e06-f58f-4b2a-bb97-2960d129f691%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[tw] Re: ThirdFlow throwing dozens of errors
Ah, I actually saw that one earlier but I haven't been able to find a way to apply it retroactively... Is there any way for this method to dynamically re-check every tiddler in the TW instance and rename whatever deserves renaming? -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/8ed789c6-e663-4232-91ed-8e5a496edceb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[tw] ThirdFlow throwing dozens of errors
My installation: standard TW5 (NodeJS version, installed globally on a Raspberry Pi, automatically launched at Raspberry reboot). I discovered ThirdFlow this morning (http://thediveo.github.io/ThirdFlow/) and was sort of interested by the tag folders functionality so I tried dragging the .tid download (plugin) to my installation. The plugin (apparently) imported correctly, adding the folders tab in the Settings tab... and then I started getting dozens of error messages. Trying to use the tag folder functionality didn't work and eventually my installation broke down and I had to manually remove the plugin and a preference file it had created. Is this soft still supposed to be relevant, and is there any reason in particular why it should have failed? The error messages started with "Sync error while processing '$:/config/FileStorage/tagfolders thirdflow", if this is any help. Thanks for reading, kodomohimari -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/3ab95ed7-37eb-40e6-9886-4b71bcc15035%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Filters not consistently catching images
... Well, actually, I just tried again with the same files (including one of the file I knew to not be caught by the filters) and it worked fine. I can't reproduce the error, every image lands where it ought to. I think I rebooted the server a couple times since last post, so I'm going to assume it was just a weird issue of filter propagation or something. For the time being, problem solved (probably by rebooting). Thanks for looking into this. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/80c3513d-d5d1-458a-a0a6-9b2645c5aeed%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[tw] Filters not consistently catching images
Soo, started experimenting with my installation (TiddlyWiki on NodeJS on a Raspberry Pi accessible through its external IP). Since I work with images a lot, I decided to try setting a filter up to have their tiddlers exist within a single folder (instead of all over the place) using this concept: http://tiddlywiki.com/#Customising%20Tiddler%20File%20Naming. My code for the file named "$:/config/FileSystemPaths" is below: [type[image/jpg]addprefix[images/]] [type[image/jpeg]addprefix[images/]] [type[image/png]addprefix[images/]] [type[image/gif]addprefix[images/]] [type[image/x-icon]addprefix[images/]] [type[image/svg+xml]addprefix[images/]] It works... but only partially, which is unnerving. Some .JPG images apparently aren't caught in the filter at all upon importing, and their files and metadata land in the tiddlers/ folder (instead of tiddlers/image/ folder). I'm not sure what makes them different from the other images that do get caught in the filter (regardless of whether they're caught, they do appear as image/jpeg when examined through TiddlyWiki). Is there any known reason why the filters might fail for some images, but not for others? (Just for the sake of data: one image that doesn't trip the filter is called IMG_0650.JPG, another that does trip it is called IMG_0637.JPG - so as far as I can tell this isn't just a matter of filename.) As a sidenote, is there any way to apply filters retroactively? For instance, if I create a tag called "map" and apply to a bunch of already imported images (or even just tiddlers), can I then apply a filter to move the tiddlers with that tag to a tiddlers/map/ folder? -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/5fc8a34c-8e45-489f-9331-a7f4dc50081d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Serving TiddlyWiki alongside other projects?
Okay, trying again after a good night's sleep solved most/all of the problems. I can access the TiddlyWiki through [home-network-IP]:8080 and I've setup port forwarding on my router to be able to reach it through [external-IP]:8080 as well (the Pi already has a fixed home-network-IP because I needed its connections to be able to survive rebooting from outside the home). It looks like the problem was mostly that I was pointing my browser at [home-network-IP]:8080/tdnotes instead. Guess next step is to setup an autolaunch in the cron-tables so the TiddlyWiki instance also survives rebooting (instead of having to manually boot it every time). Any hint towards running multiple instances, in case I decide to dig in that direction? (The whole [IP]:8080/folder1 existing concurrently to [IP]:8080/folder2 thing.) Thanks a lot for your help, kodomohimari On Monday, September 4, 2017 at 4:08:23 AM UTC+2, RichardWilliamSmith wrote: > > is accessed through localhost:8080 (edit and save work well). >> localhost:8080/tdnotes gives a 404 > > > Even though the files for your wiki may be in the path being served by > Apache (at localhost:80/tdnotes or leave the 80 off altogether) but the > wiki, as a wiki, is being served on a different process altogether - > localhost:8080 and the root of what its serving is the tdnotes folder. > > Just to be clear - the Tiddlywiki server would work even without Apache - > they are completely independent things. > > When you're accessing your Pi from another computer, it is no longer the > "localhost". You need to use its ip address instead (probably assigned to > it by your router). You should be able to find if by running ``ifconfig`` > > > On Monday, September 4, 2017 at 9:24:38 AM UTC+10, kodomohimari wrote: >> >> At the current time, the TiddlyWiki runs in a node I start manually by >> going to www in CLI and is accessed through localhost:8080 (edit and save >> work well). localhost:8080/tdnotes gives a 404 (which I assume is because >> Apache isn't grabbing the 8080 port which means localhost:8080/tdnotes >> actually points to an entirely different location). >> >> Having to add the :8080 is not "the" breaking issue, though (thanks for >> clarifying the ports thing) - I'm completely unable to reach the TiddlyWiki >> through any other computer than the Pi itself (i.e. through its own >> browser). Both [home-network-IP]:8080 [external-IP]:8080 seems to fall in >> an absolute limbo on my other computers. >> >> Ultimately, I'd like to be able to setup multiple instances (for >> instance: :8080/tdnotes, :8080/project, etc.), but at the current time I >> can't reach any instance at all from outside the Pi. >> >> Regards, >> kodomohimari >> >> On Monday, September 4, 2017 at 12:41:58 AM UTC+2, RichardWilliamSmith >> wrote: >>> >>> Hi, >>> >>> You have Apache running on port 80 to serve static files. The Tiddlywiki >>> server needs to run as a separate process alongside that, on a different >>> port, and they are accessed as two different services. >>> >>> If you really need to be able to access both services from the same >>> port, I guess you will need to configure apache to pass requests to the >>> other port (your google is as good as mine - >>> https://stackoverflow.com/questions/8541182/apache-redirect-to-another-port >>> ?) but I doubt it's worth the trouble. >>> >>> Do you have the tiddlywiki process actually started on the Pi? Are you >>> able to access it through :8080/tdnotes ? >>> >>> Regards, >>> Richard >>> >>> On Monday, September 4, 2017 at 6:55:46 AM UTC+10, kodomohimari wrote: >>>> >>>> Just discovered TiddlyWiki and I'm trying to set it up with nodejs on >>>> my Raspberry Pi (which I use for multiple purposes, including as a web >>>> development server). >>>> >>>> The Pi is setup so that a folder named www in its Desktop corresponds >>>> to the landing folder when reached from a browser (i.e. pointing a browser >>>> at my IP reaches the Apache top page, from where I can access various >>>> projects stored in folders in www i.e. www/project1). >>>> >>>> I'm trying to set up a situation where www/tdnotes is where the >>>> TiddlyWiki lives, and it can be reached as any other project on the Pi >>>> through [IP]/tdnotes. Two obstacles on my path: >>>> >>>> - The folder location. If I just aim for [IP], I'm landing on my Apache >>>> top page (which is normal
[tw] Re: Serving TiddlyWiki alongside other projects?
Hmm... I have no such file in www/tdnotes, there is only the tiddlywiki.info file, a folder called tiddlers and in that folder a file called $__StoryList.tid. Which does seem odd now that I think about it, I don't even see the welcome screen here even though it's displayed when I access the TiddlerWiki through localhost:8080. Is there some aliasing going on? On Monday, September 4, 2017 at 12:43:41 AM UTC+2, TonyM wrote: > > kodomohimari > > Did you rename your tiddlywiki, in the folder to index.html so as to make > it the default? > > Tony > > On Monday, September 4, 2017 at 6:55:46 AM UTC+10, kodomohimari wrote: >> >> Just discovered TiddlyWiki and I'm trying to set it up with nodejs on my >> Raspberry Pi (which I use for multiple purposes, including as a web >> development server). >> >> The Pi is setup so that a folder named www in its Desktop corresponds to >> the landing folder when reached from a browser (i.e. pointing a browser at >> my IP reaches the Apache top page, from where I can access various projects >> stored in folders in www i.e. www/project1). >> >> I'm trying to set up a situation where www/tdnotes is where the >> TiddlyWiki lives, and it can be reached as any other project on the Pi >> through [IP]/tdnotes. Two obstacles on my path: >> >> - The folder location. If I just aim for [IP], I'm landing on my Apache >> top page (which is normal). If I aim for [IP]/tdnotes, I reach it through >> the Apache interface (i.e. I don't enter the TiddlyWiki, I just see its >> file structure externally). >> - The port number. Is there a way to get rid of it i.e. just type >> [IP]/tdnotes instead of [IP]:8080/tdnotes? (For instance, I suppose >> changing the port number served by the TiddlyWiki server could work, but >> can it serve the same port as HTTP i.e. 80?) >> >> I have a feeling the issues are interconnected, but I'm clueless as to >> how to proceed forward. Any hint would be greatly appreciated. >> >> -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/53b3ac10-c9b6-409e-bcce-d0bbd16d4ac7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Serving TiddlyWiki alongside other projects?
At the current time, the TiddlyWiki runs in a node I start manually by going to www in CLI and is accessed through localhost:8080 (edit and save work well). localhost:8080/tdnotes gives a 404 (which I assume is because Apache isn't grabbing the 8080 port which means localhost:8080/tdnotes actually points to an entirely different location). Having to add the :8080 is not "the" breaking issue, though (thanks for clarifying the ports thing) - I'm completely unable to reach the TiddlyWiki through any other computer than the Pi itself (i.e. through its own browser). Both [home-network-IP]:8080 [external-IP]:8080 seems to fall in an absolute limbo on my other computers. Ultimately, I'd like to be able to setup multiple instances (for instance: :8080/tdnotes, :8080/project, etc.), but at the current time I can't reach any instance at all from outside the Pi. On Monday, September 4, 2017 at 12:41:58 AM UTC+2, RichardWilliamSmith wrote: > > Hi, > > You have Apache running on port 80 to serve static files. The Tiddlywiki > server needs to run as a separate process alongside that, on a different > port, and they are accessed as two different services. > > If you really need to be able to access both services from the same port, > I guess you will need to configure apache to pass requests to the other > port (your google is as good as mine - > https://stackoverflow.com/questions/8541182/apache-redirect-to-another-port > ?) but I doubt it's worth the trouble. > > Do you have the tiddlywiki process actually started on the Pi? Are you > able to access it through :8080/tdnotes ? > > Regards, > Richard > > On Monday, September 4, 2017 at 6:55:46 AM UTC+10, kodomohimari wrote: >> >> Just discovered TiddlyWiki and I'm trying to set it up with nodejs on my >> Raspberry Pi (which I use for multiple purposes, including as a web >> development server). >> >> The Pi is setup so that a folder named www in its Desktop corresponds to >> the landing folder when reached from a browser (i.e. pointing a browser at >> my IP reaches the Apache top page, from where I can access various projects >> stored in folders in www i.e. www/project1). >> >> I'm trying to set up a situation where www/tdnotes is where the >> TiddlyWiki lives, and it can be reached as any other project on the Pi >> through [IP]/tdnotes. Two obstacles on my path: >> >> - The folder location. If I just aim for [IP], I'm landing on my Apache >> top page (which is normal). If I aim for [IP]/tdnotes, I reach it through >> the Apache interface (i.e. I don't enter the TiddlyWiki, I just see its >> file structure externally). >> - The port number. Is there a way to get rid of it i.e. just type >> [IP]/tdnotes instead of [IP]:8080/tdnotes? (For instance, I suppose >> changing the port number served by the TiddlyWiki server could work, but >> can it serve the same port as HTTP i.e. 80?) >> >> I have a feeling the issues are interconnected, but I'm clueless as to >> how to proceed forward. Any hint would be greatly appreciated. >> >> -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/9cfc9700-4df5-4690-b1d8-2f00a596f152%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[tw] Serving TiddlyWiki alongside other projects?
Just discovered TiddlyWiki and I'm trying to set it up with nodejs on my Raspberry Pi (which I use for multiple purposes, including as a web development server). The Pi is setup so that a folder named www in its Desktop corresponds to the landing folder when reached from a browser (i.e. pointing a browser at my IP reaches the Apache top page, from where I can access various projects stored in folders in www i.e. www/project1). I'm trying to set up a situation where www/tdnotes is where the TiddlyWiki lives, and it can be reached as any other project on the Pi through [IP]/tdnotes. Two obstacles on my path: - The folder location. If I just aim for [IP], I'm landing on my Apache top page (which is normal). If I aim for [IP]/tdnotes, I reach it through the Apache interface (i.e. I don't enter the TiddlyWiki, I just see its file structure externally). - The port number. Is there a way to get rid of it i.e. just type [IP]/tdnotes instead of [IP]:8080/tdnotes? (For instance, I suppose changing the port number served by the TiddlyWiki server could work, but can it serve the same port as HTTP i.e. 80?) I have a feeling the issues are interconnected, but I'm clueless as to how to proceed forward. Any hint would be greatly appreciated. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/1669141f-4b0f-4c5b-b35e-994dbb8ba601%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
