[tw5] Re: Taking Node Server to the next level

Hello All, As I'm currently in the research phase in the same direction (which is very interested to me), please check my two cents https://gohugo.io/ and its Github Repo , Best Regards Mohamed Amin On Friday, November 29, 2019 at 1:59:43 AM UTC+2, Arlen

[tw5] Re: Taking Node Server to the next level

Bimlas I would love to enable contributions to tiddler content via got hub a bit like when you edit tiddlywiki.com but have the changes appear online. We could open our published editions to issues and changes. But your idea sounds even better. Regards Tony -- You received this message

[tw5] Re: Taking Node Server to the next level

There are two things that I think can be used for online storage: On the one hand, the GitHub saver could be upgraded to save the tiddlers one at a time using the datafolder format instead of a large HTML (so you wouldn't have to wait minutes to save, just wait for one tiddler to save, like

Re: [tw5] Re: Taking Node Server to the next level

Cozy link: https://docs.cozy.io/en/tutorials/konnector/scrape-data/ > Another option is Cozy, which, if I understand it, is a free online cloud. > This does not require the PouchDB saver, but a unique one, but may be used. > If I have more time, I'll dig into the saver world more. > -- You

Re: [tw5] Re: Taking Node Server to the next level

Arlen, Jed, Thank you for supporting the community with your knowledge! Big respect! Database backends look really useful. If I understand it, maybe even PouchDB can be solved online by Glitch: https://glitch.com/~pouchdb-server (click on show to fetch some data). Another option is Cozy,

Re: [tw5] Re: Taking Node Server to the next level

And here's the link for it: https://github.com/Arlen22/TW5-storage-plugin On Mon, Dec 2, 2019 at 1:49 PM Arlen Beiler wrote: > Well, Jed's adapter and everyone's thoughts so far inspired me to do a > little exploring and I managed to put this little proof of concept > together. It turned out I

Re: [tw5] Re: Taking Node Server to the next level

Well, Jed's adapter and everyone's thoughts so far inspired me to do a little exploring and I managed to put this little proof of concept together. It turned out I did not need to touch the client at all and only modify four routes on the server. What's nice is that the index is still generated as

Re: [tw5] Re: Taking Node Server to the next level

I think in this case I'm rather aiming to build something new on top of TiddlyWiki5. I may revisit the rest of the TiddlyWeb protocol at a later time and take some ideas from it. However, I think that to build something new it would need to be built using TiddlyWiki5 from the ground up, whereas

Re: [tw5] Re: Taking Node Server to the next level

PouchDB is a very good first step because of the way it is setup. SQLite would also be a great first step for targeting SQL databases. On Sun, Dec 1, 2019 at 9:30 PM TonyM wrote: > Jed, > > Great work, what a Wiz. I will have a closer look. With the pouchDB have > any more persistence that

Re: [tw5] Re: Taking Node Server to the next level

TonyM wrote: > > I do have a possibly faulty distant memory of a tiddlywiki writing to a > Google sheet. > I *think* Mat did that ... hang-on ... yes: https://groups.google.com/d/msg/tiddlywiki/QcTOJCVXkDw/kS5VBW0ACQAJ It uses Google Forms & Spreadsheets. Best TT -- You received this

Re: [tw5] Re: Taking Node Server to the next level

Jeremy I do have a possibly faulty distant memory of a tiddlywiki writing to a Google sheet. I found it curious but it had no use case for me at the time. I will see if I can find anything. We are spoilt for choice in some ways yet I feel we need to remove a few speed humps. Regards Tony

[tw5] Re: Taking Node Server to the next level

Why not to reuse Tiddlyweb/Tiddlyspace work? - It has MySQL backend - It is multiuser and allows concurrent editing - It has public and private spaces - It uses the standard Node.js sync-adaptor - It works with TWC as well IMO it is a great piece of software. Not easy to set up.

Re: [tw5] Re: Taking Node Server to the next level

There have been quite a few experimental syncadaptors over the years. Some of them come back from a simple GitHub search: https://github.com/search?q=syncadaptor I went through the first couple of pages and found: * an old syncadaptor for CouchDB: https://github.com/cjxgm/tearly/ * a

[tw5] Re: Taking Node Server to the next level

It is stored locally on the hard drive like other node wikis, the difference is that this is stored in some database files instead of individual tiddler files. It is not localStorage or a browser based solution. If you use the browser based version of pouchdb it is generally built on top of

[tw5] Re: Taking Node Server to the next level

Jed, Great work, what a Wiz. I will have a closer look. With the pouchDB have any more persistence that local storage I wonder? Such node solutions are great but we must find an easy way to host such things online when needed. Regards Tony On Monday, December 2, 2019 at 10:06:26 AM UTC+11,

[tw5] Re: Taking Node Server to the next level

After finding out that I have very little idea how syncadaptors work I started playing with making a new one and ended up with a working pouchdb syncadaptor. It is very rough but it works, it will create a database and save tiddlers to it, delete them when appropriate and then load the

Re: [tw5] Re: Taking Node Server to the next level

Most Node solutions that I am aware of are either request-based (AWS Lambda and Cloudfront Workers), or VM based. There's also Heroku, but it doesn't allow a persistent file system. However, the data storage structure is a more serious bottleneck for innovation, I believe, and once we have a

[tw5] Re: Taking Node Server to the next level

Cont... Sorry. Mobile gg can be a pain. I understand Jed has done a lot of on securing bob when internet facing. So what I am asking is if node where more common on hosting and safe to open to the internet could we not focus on a smaller subset of technologies with similar outcomes? Of

[tw5] Re: Taking Node Server to the next level

Npm node etc... Is really easy to use locally and to serve to local area networks inside a firewall. However as pointed out by Jed this can be a liability on mobile computers joining other networks. This can be managed. My wholesale host let me install node internet facing but its not a

[tw5] Re: Taking Node Server to the next level

I was thinking of remote hosting and CPanel. I found there was pretty much no support for that or any easy equivalent. But if it can be installed locally with NPM, then that could be interesting. On Friday, November 29, 2019 at 10:54:14 AM UTC-8, Jed Carty wrote: > > Mark, > > The benefit of

Re: [tw5] Re: Taking Node Server to the next level

I'm kind of thinking that if the user is setting up MySQL themselves, then they have control of the server and might as well be setting up TiddlyServer or Bob anyway, unless MySQL is up their alley, in which case it's no big deal. On the flip side, using PouchDB or SQLite instead of the file

[tw5] Re: Taking Node Server to the next level

Mark, The benefit of PouchDB is that it can be installed using NPM, or packaged into something like BobEXE without having to do a system-wide installation. For a local installation PouchDB is much easier to set up than MySQL/MariaDb. If you didn't go the packaged route like BobEXE it would at

[tw5] Re: Taking Node Server to the next level

The problem with solutions like PouchDb is that there are no turn-key installations. You have to pretty much do everything yourself down to the bare metal. SQL, on the other hand, is supported almost everywhere. The workaround re fields is to specify the fields you want in advance. Rebuild

[tw5] Re: Taking Node Server to the next level

On Friday, November 29, 2019 at 12:45:17 PM UTC+1, Jed Carty wrote: ... > Running a ArangoDB for hosting peoples tiddlywiki like tiddlyspot would > probably work well, I am less certain about local installations. > You are on the point. I do have similar concerns about every database ... They

[tw5] Re: Taking Node Server to the next level

ArangoDB looks very interesting as an option. I haven't run into any multi-modal databases like that before. It does look like the data model is just about ideal for tiddlywiki in terms of storing tiddlers and full html files, storing html files as a string shouldn't be a problem. A quick

[tw5] Re: Taking Node Server to the next level

One more thing: - The cool thing about DAT is, that it will nicely run on a raspberry pi 3, with a big harddrive attached. -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,

[tw5] Re: Taking Node Server to the next level

Some more thoughts. The problem with databases I see are: - *Our users like files* and will go a long way to keep it that way. - DBs need maintenence - DBs need to be secured - ... So in the end we need a service provider, that abstracts the complexity away. I personally would like to

[tw5] Re: Taking Node Server to the next level

Hi, If you would want to have a cool new database ArangoDB may be an option. ArangoDB is the open-source native multi-model > database for graph, document, key/value and search needs. So we could store tiddlers as "documents" and add some graph info to create a

[tw5] Re: Taking Node Server to the next level

A while ago I made a syncer that used sqlite and from that I wouldn't suggest a relational database, SQL seems like it would be almost perfect for storing tiddlers but I immediately ran into problems with the database schema because aside from text, title, tags, created, type and modified you

[tw5] Re: Taking Node Server to the next level

Arlen, I would think this a great idea. SQLite, MariaDB etc... could be used. I use a cpanel account on a hosting service and often jump in behind the scenes to manipulate databases. It would be quite easy to define additional databases with an sql script designed for Tiddlers or TiddlyWikis.