Hi Gregorio, Some argue those discussions best go into the dev group or the GitHub issues as there's sooo much tech-stuff in here...
> I'm looking for some help in achieving a self-hosted TiddlyWiki solution, > preferably with node.js: > Personally, I'd shy away from node.js hosting for atm, as it seems a rather expensive, both in terms of cost and effort... which I would think was worth it if one was planning to create some node-based TiddlySpot-like multi-user-environment. > > - I want to be able to go to wiki.mydomain.com > - login/authenticate so I can edit tiddlers. > > The basic approach I'd pursue is to have the wiki using some readonly template with you knowing how to switch that to enable editing features. With a wee bit of testing you can easily create bookmarks <http://tb5.tiddlyspot.com/#Creating%20Smart%20Bookmarklets> that help you toggle things. > > - no other visitor/user can edit. > > Again, it's all in the theme. Of course, some smarty-pants may try to hack your implementation. However, saving back to the server does require authentication... so keep your password(s) safe. > > - have those changes automatically saved > > So long as you're the one and only editor to your wiki(s) that can alternatively be done without node.js, using store.php <http://tb5.tiddlyspot.com/#Your%20own%20TiddlySpot-like%20upload%20server> . > > - Locally, I'd also like to be able to manipulate what tiddlers show > up on wiki.mydomain.com. > > That does indeed require a node.js enbironment. But perhaps there is some simple workflow to first update / sync your local tiddlers with whatever you last edited online. Then you would go editting locally and build that next tiddlywiki. I would personally hit save in the browser to have store.php <http://tb5.tiddlyspot.com/#Your%20own%20TiddlySpot-like%20upload%20server> do the uploading... but sure, a node.js server is, all in all, the more extensible ecosystem, although somewhat bound to your machine. > > - Say I keep a project specific wiki local until it goes live, I'd > like to be able to easily integrate those local tiddlers with the live > ones. > > Recently, Jeremy or someone in the community proposed a TiddlySpot based workflow <http://tb5.tiddlyspot.com/#Documentation> to enable those who want to contribute but shy away from GitHub submit edits for TiddlyWiki.com back to those who actually manage the repo, i.e. Jeremy. I wonder if there's any progress on those sync-/import-scripts, as they will surely help putting online-edited tiddlers back into a local node.js store to then bake and push the next updates having merged any online changes. Perhaps a simple "modified" check will do the trick, perhaps an aliased "last-titles" field will also be beneficial and could help redirect otherwise broken links to the new location. > > - As far as I understand this can be achieved with the tiddlywiki CLI, > but I'm not clear on that yet. > > Yes, the node.js build process is console driven, atm. Although it's not entirely unthinkable that some (hopefully) cross-platform desktop-app-development-guru might create a graphical UI to edit your editions' tiddlywiki.info (or even package.json), adding / deleting themes, plugins, an edition folder, and provide a few customizable build-commands / command-sequences, so you don't have to do all the typing to, say, also get that static output. Would be even cooler if you could actually set-up and trigger these things from within TiddlyWiki itself. Would be a really good reference project for TiddlyWiki as an app with a certain degree of desktop integration. I've looked at hosting solutions like heroku and openshift, but the issue I > have is I'm not sure what the correct approach is.. these platforms don't > seem to use NPM so do I need the tw5 repo in the root of my app? > Besides associated costs, all these questions are precisely why I would shy away from that atm. But I guess you would have to manually push that latest TiddlyWiki build to your sever and set-up whatever environment voodoo is needed to actually run required build / server scripts. So, @PMario, that's perhaps one reason why building TW via npm & package.json is not quite a viable solution for those lacking npm. > What is the correct folder structure in this scenario? > Something that resembles the official repo structure <https://github.com/Jermolene/TiddlyWiki5/issues/823>, leaving out whatever bit's you're not actually creating yourself, especially the core. Meaning, I would have these folders separated... /TiddlyWiki5/ /MyRepo/ > Do I put the tw5 repo in a sub-folder and create folders with > tiddlywiki.info for my wikis? > You don't have to have the core in your repo. Instead, set certain environment variables <http://tiddlywiki.com/dev/#Scripts%20for%20building%20tiddlywiki.com> for the build scripts to find your build environment and whatever components you wish to mingle. > Or do I just create folders for my wikis in the tw5 repo root? > I wouldn't recommend it. Just follow the folder structure but don't pull code into your (commit-) folders that are not maintained / created by yours truly. > And with the above in mind, how can I start a TiddlyWiki with "node > tiddlywiki.js"? As most of these PaaS seem to require a "Procfile" with > such a command. > I think we're quite some mileage away from calling TiddlyWiki a full-fledged PaaS. As for Procfile, one more thing I had yet to hear about for the first time. > My apologies if these questions are obtuse, I'm still learning the Tiddly > ways. ;) > These questions are all very important and their answers are interesting to all who wish to build TiddlyWiki-based-solutions, if "only" websites... and are looking for the least painful way to... - host TiddlyWiki(s) - sync online changes with a local repo / dev / build environment - for which a direct per-tiddler-syncer with some server edition is probably the least painful way. albeit costly with node ...besides *store.php*, bidix also had a script that allowed uploading individual TWc tiddlers... but his TiddlyHome site appears to be gone and so are his scripts. Unless perhaps... https://code.google.com/p/bidix/source/browse/trunk/iTW/storeTiddler.php?r=156 So, with a little fiddling for making that work with tw5, i.e. syncing with a php based folder structure, and then some app that allows to sync that folder structure via ftp with your desktop environment, you could pull things from a php driven hoster back to your local environment, compare tid files, assuming the same folder structure on both ends. What a load of text. ^^ Best wishes, Tobias. -- 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
