Embed Tiddlywiki within a database driven website

207 views
Skip to first unread message

Paul P

unread,
Sep 8, 2017, 6:43:30 PM9/8/17
to TiddlyWiki
Hi

I want to embed multiple Tiddlywikis within an existing database driven web application. Think of this as a database of Tiddlywikis.

I am new to Tiddlywiki. My hope is to store the entire Tiddlywiki as text in a database via the web application such that I can retrieve and save in the same way as any other text field. The entire Tiddlywiki would be stored in the database. I would add a button on a screen in the web application that would allow the user to "Open the Tiddlywiki", which would use the text from this new field which stored the wiki page, similar to the way the entire wiki can be saved to a local file. If that is not the way to go, then maybe some pointers on how to save just the data (as json, but again, to a text field on a screen). Ideally, installed plugins would be saved also. The idea is to store the wiki almost as it is a new "field type" along with other fields on an existing screen. I would rather not send directly to a server, as I cannot control too much of what the server will accept. But it will accept and return text fields so I hope to use that.

Any ideas on how to proceed? Thank you!

TonyM

unread,
Sep 9, 2017, 8:12:58 PM9/9/17
to TiddlyWiki
Paul,

I do not have an answer but have you looked at the way noteself used couchdb and pouchdb?

Tony

Abraham Samma

unread,
Sep 11, 2017, 5:59:15 AM9/11/17
to TiddlyWiki
Hi Paul,

It is absolutely possible. I'm actually working on building one right now myself; originally for my own use but now I'm designing it for eventual public use. I'm making use of couchdb as my database. I suggest you look at the source code for the put saver module to get an idea of how you might implement what're you're suggesting.

Regards

Paul P

unread,
Sep 11, 2017, 10:56:06 AM9/11/17
to TiddlyWiki
This is of interest. https://noteself.github.io/ I cannot run CouchDB however maybe I can use the same concepts.

So far I am uncertain as to the best approach to take. Because of the size of even an empty tiddlywiki I am leaning toward storing each as a separate file on the server upon save of the wiki. I am thinking this helps ensure each tiddlywiki is "future proof" because each is fully self contained. Newer versions of tiddlywiki will not affect older versions.

However this is all new to me and so I may be mistaken on some basics.

Abraham Samma

unread,
Sep 11, 2017, 6:14:17 PM9/11/17
to tiddl...@googlegroups.com
You can also check out TiddlyServer 2.0 which I use to serve my own wiki on my local machine.

https://github.com/Arlen22/TiddlyServer

TonyM

unread,
Sep 11, 2017, 8:00:24 PM9/11/17
to TiddlyWiki
Paul,

Please look around at the various implementation and hosting opportunities with TiddlyWiki, I suspect you will get closer to an answer if you do that. The Save and Hosting subject is a big one in TiddlyWiki given browser compatibility and future security changes.

Perhaps voice why you asked in the lead question, fill out your use case and there may already be a solution. If you ask specific questions your are more likely to get specific answers, however it sounds like you are seeking a general or systematic solution.

Regards
Tony

Danielo Rodríguez

unread,
Sep 14, 2017, 4:17:34 PM9/14/17
to TiddlyWiki
If you want to store the wiki within the database then the couchdb adaptor is exactly what you need, Noteself only used the database as an external storage .

Regards

Danielo Rodríguez

unread,
Sep 14, 2017, 4:23:01 PM9/14/17
to TiddlyWiki
If someone is going to build a plug-in to serve or store wikis from a couch-like database you should know that you are going to re-invent the wheel. After some years around this scene I see this is quite common
Reply all
Reply to author
Forward
0 new messages