It *is* complicated. Not exactly an easy solution, and usually not free. I suspect your university wouldn't want non-IT people setting up public-facing PHP-based servers.
On Thursday, December 3, 2020 at 11:31:54 PM UTC-8 springer wrote: > Hi Tones, > > To folks who speak server-talk, phrases like "a standard php server with > tw-receiver" and "the store.php" are surely as clear as day. And I > appreciate that your reply is a gesture of generous helpfulness. > > To someone like me, unpacking even those casual phrases is a risky > investment of time. Even assuming that the server space I can use at my > university is/has "standard" php (though I wouldn't know how to check > that), I don't grasp what it would take to equip (?) it with tw-receiver, > or whether tw-receiver lives (?) there at the server (and may require > getting an IT person to approve/help) or whether "receiver" implies that I > need to get it set up (?) at my end... , etc. > > Yes, I could grope around for some clarity on these matters... OK... a > quick google gets me as far as this page > <https://github.com/sendwheel/tw-receiver>, where I learn that > tw-receiver apparently has both a tw-plugin component and a server-side > file to install... ok... But then a bit further along I read that "You will > likely have to make server side adjustments; things like setting directory > permissions or ini configurations like max upload sizes". Meh. This is more > server-speak; it assumes that I can orient to whether and how I need to > make adjustments to "ini configurations" and "things like that" ([insert > emoji for blank stare]) ... and having never done anything at all with php > before, I just can't tell how long, or how steep, this learning-curve will > be, and what the odds are that, one or two hours in, I'll hit a brick wall > of some kind. > > The only reason I was able to work it out with GitHub was because of > Mohammad's very careful step-by-step tutorial, written so that even I could > understand it. Might something comparable be available for setting up a php > server and getting tw-receiver up and running with it? > > (As I mentioned to Alvin, I'm pretty content with the GitHub saver for > now, since it really does let TW5 behave over https in the Tiddlyspot way. > But I'm replying on behalf of other muggles who feel stranded by the loss > of tiddlyspot.) > On Thursday, December 3, 2020 at 9:41:15 PM UTC-5 TW Tones wrote: > >> Springer, Alvin. >> >> Now days I only access my legacy TWC files via TiddlyDesktop, But TW5 is >> fine to host on a standard php server with tw-receiver. I believe the >> store.php used to work with TWC and >> I believe this has being discussed in >> https://groups.google.com/g/tiddlywikiclassic. >> >> Otherwise its easy to use Timimi from my desktop on a webdisk or that is >> synchronised. >> >> Tones >> >> Tones >> On Friday, 4 December 2020 at 13:05:04 UTC+11 springer wrote: >> >>> Alvin, >>> >>> I agree that losing TiddlySpot is a pain for anyone who really needs TW >>> projects to be both spontaneously edited (from anywhere) and instantly >>> available via a potentially-public url. >>> >>> GitHub is the only solution I've found that does meet these conditions >>> (without being a server administrator or being a coding expert). >>> >>> The good news: As soon as you successfully set up GitHub once >>> (configuring the right authentication for saving), adding additional >>> tiddlywiki files in the same "repo" (repository) is VERY easy. Unlike >>> tiddlyspot, you can have even GitHub use the same password authentication >>> handshake for each of your five wikis. As with tiddlyspot, once the >>> password is set up on a given computer-browser system (and especially if >>> you configure auto-save), future visits are just smooth as can be. >>> >>> I also have domain names and access to server space, but have not yet >>> found a way to use these resources to set up TW5 projects so that they are >>> editable over https: browser access. In theory, GitHub can be a >>> ventriloquist and allow your files to be accessed by way of your custom >>> domain name's url system. So far, my attempts to follow directions to set >>> that up have stumbled. So I can't confirm that it's easy, but I'm >>> determined to return to the question when I have another chunk of >>> troubleshooting time on my hands. In the meantime, I'm finding the >>> github.com urls fairly easy to work with. >>> >>> -Springer >>> >>> On Thursday, December 3, 2020 at 5:36:56 PM UTC-5 Alvin wrote: >>> >>>> Thank you to everybody that has replied. >>>> >>>> I have about five tiddlyspot files, and it's not clear to me if I can >>>> use GitHub for all of them. >>>> >>>> I have a little experience with Dropbox, enough that I closed my >>>> account less than a week after I created it. So I don't want to use >>>> Dropbox. >>>> >>>> I have a domain or two, and I can create subdomains, so I'd like to do >>>> that. >>>> >>>> Again, my tiddlyspot files are ClassicTW, and I want to keep them >>>> password protected. A step-by-step how to port them is what I'm looking >>>> for. >>>> >>>> I'm sure I'm not the only person looking for this. It's are real payne >>>> in the arse not being able to update my Tiddlyspot files. >>>> >>>> On Friday, November 27, 2020 at 8:56:26 AM UTC-6 springer wrote: >>>> >>>>> TiddlySpot was absolutely the lowest bar-to-entry for >>>>> instant-gratification create-edit-save-publish work in TiddlyWiki. Having >>>>> something like it is essential to attracting new users with an interest >>>>> in >>>>> public-facing instant-edit projects. >>>>> >>>>> Alvin: For those like you who already know they love tiddlywiki and >>>>> love the tiddlyspot convenience, I do recommend the GitHub saver. It's >>>>> effectively the same workflow experience as TiddlySpot... at least it's >>>>> comparable *AFTER* the arduous process (at least, it was arduous for me) >>>>> of >>>>> getting the repository set up and properly cleared for saving from the >>>>> browser. Mohammad's walkthrough tutorial is very helpful (and it seems >>>>> like >>>>> the glitch around GitHub email verification, which hobbled my own >>>>> experience, was idiosyncratic). >>>>> >>>>> -Springer >>>>> On Friday, November 27, 2020 at 5:57:31 AM UTC-5 Ste wrote: >>>>> >>>>>> Just to edit my response, now I've actually read the thread >>>>>> carefully, oops, I'm slightly off track in my reply...I'm just looking >>>>>> at >>>>>> individual hosting. I'd happily chuck some cash somebody's way for >>>>>> continued tiddlyspot workingness. I'm guessing no one has heard >>>>>> anything >>>>>> regarding the future of the site? >>>>>> >>>>>> On Friday, 27 November 2020 at 10:48:32 UTC Ste wrote: >>>>>> >>>>>>> I'm looking at this at the moment...I keep thinking..'Oh..I'll just >>>>>>> edit this' on my wiki, then cry quietly as I remember that tiddlyspot >>>>>>> is >>>>>>> broken :( >>>>>>> I was thinking node.js with bob to serve multiple wikis. >>>>>>> So far Iv'e turned up https://www.mythic-beasts.com/ for about £70 >>>>>>> a year...I think, or a combo of Domain reg from google, Hosting from >>>>>>> https://www.cloudflare.com/ and serving from >>>>>>> https://www.vultr.com/products/cloud-compute/ at $2.50 a month. I >>>>>>> haven't committed to anything yet....Going to boot up my pi and check I >>>>>>> manage to get it all running before I throw cash after it. The joys of >>>>>>> the >>>>>>> command line..... >>>>>>> >>>>>>> Ste >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Thursday, 26 November 2020 at 21:59:07 UTC Mark S. wrote: >>>>>>> >>>>>>>> I'm thinking as far as an offer goes, you might have the most luck >>>>>>>> posting at https://tiddlyspot.blogspot.com/ . With or without >>>>>>>> chocolate. >>>>>>>> >>>>>>>> For setting up your own, you would need to find a web host, >>>>>>>> preferably one that charges per space used rather than >>>>>>>> un-metered-but-with-secret-restrictions. Then you would use store.php >>>>>>>> (older) or tw-receiver to serve up your own tw host. There might be >>>>>>>> additional complications if you wanted to protect your files via ssl. >>>>>>>> When >>>>>>>> I looked at hosts, it seemed that most of them wanted to sell one rate >>>>>>>> for >>>>>>>> 1 to 3 years, and then twice that rate afterwards. Most of them that >>>>>>>> charge >>>>>>>> per storage space were more expensive. For a personal site, I might >>>>>>>> just >>>>>>>> depend on TW's own encryption rather than worrying about a site >>>>>>>> getting >>>>>>>> hacked. >>>>>>>> >>>>>>>> Re hosting for everyone, all the public files listed in the >>>>>>>> tiddlytoolmap seem to come to about a half gig. So if the total space >>>>>>>> was >>>>>>>> under one gig, then there's at least one website offering services at >>>>>>>> $6/month plus probably $14/year for domain name registration. >>>>>>>> >>>>>>>> The question of size keeps coming up. It's hard to estimate how >>>>>>>> much a site would cost when the total size is unknown. >>>>>>>> >>>>>>>> Well, this probably hasn't helped much, but should prompt other >>>>>>>> conversations. >>>>>>>> >>>>>>>> Good luck! >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Thursday, November 26, 2020 at 12:51:27 PM UTC-8 Alvin wrote: >>>>>>>> >>>>>>>>> Happy Thanksgiving, everybody. >>>>>>>>> >>>>>>>>> Did my question fall through the cracks? I don't think it can get >>>>>>>>> COVID-19, so there's no need to social distance. Would it help if I >>>>>>>>> offered >>>>>>>>> chocolate for an answer? >>>>>>>>> >>>>>>>>> On Monday, November 16, 2020 at 12:24:15 PM UTC-6 Alvin wrote: >>>>>>>>> >>>>>>>>>> I offered to foot the bill for another hosting service for Simon >>>>>>>>>> and Daniel to use to move the TiddlySpot domain, but all I've heard >>>>>>>>>> so far >>>>>>>>>> is crickets. So I would like to take my ClassicTW files that were on >>>>>>>>>> TiddlySpot and put them online somewhere else. I would appreciate it >>>>>>>>>> if >>>>>>>>>> anyone can provide step by step instructions how to do that. I also >>>>>>>>>> need to >>>>>>>>>> know how to keep them password protected. Thank you so much. >>>>>>>>>> >>>>>>>>>> If someone wants to contact me (Alvin dot Orzechowski at sign >>>>>>>>>> gmail dot com) about my offer, please do so directly. >>>>>>>>>> >>>>>>>>> -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/5253f25c-7a7e-4783-a175-0cd0ffcf9395n%40googlegroups.com.
