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 <mohammad.rahm...@gmail.com> 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 <cyn...@gmail.com> 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 and perhaps different style (CSS) customizations. >>>>> >>>>> I came across this Github issue thread >>>>> <https://github.com/Jermolene/TiddlyWiki5/issues/3069> where Tobi >>>>> Beer (awesome work BTW!) presented some dirty implementation >>>>> <https://tobibeer.github.io/TiddlyWiki5> of a "monolithic" based >>>>> multiple wiki approach. Without going into details of current discussion >>>>> regarding that topic: What would be the most easiest way to achieve what >>>>> I've described before? >>>>> >>>>> Thanks in advance. >>>>> >>>>> >>>>> Greetings, >>>>> Victor >>>>> >>>>> -- >>> 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/ba669f2e-af48-407b-9e6c-3d0db1f905bc%40googlegroups.com >>> <https://groups.google.com/d/msgid/tiddlywiki/ba669f2e-af48-407b-9e6c-3d0db1f905bc%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- > 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/bf9966d6-5cc1-4b48-a5c3-9a80083861a7%40googlegroups.com > <https://groups.google.com/d/msgid/tiddlywiki/bf9966d6-5cc1-4b48-a5c3-9a80083861a7%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/CAJ1vdSRZ2uyNqyEByHTV-eb9YrAAm%2BjhOeP-OaWOhrqu252UEQ%40mail.gmail.com.
