Hello Jose,
Maybe you could check the couchadaptor
https://github.com/wshallum/couchadaptor
It requires a small setup in one couchdb provider. But any couchdb provider
will give you:
* Free hosting onf the TW file as an attachment
* Free storage for your tiddlers
* Revisions
* Users management
For a running example of this you can check my test wiki
https://danielo515.cloudant.com/tw/_design/tw/index.html
El viernes, 22 de mayo de 2015, 0:45:35 (UTC+2), Danielo Rodríguez escribió:
Hello Jose,
Maybe you could check the couchadaptor
https://github.com/wshallum/couchadaptor
It
On Mon, 2 Mar 2015, Tobias Beer wrote:
Not knowing how socialuser works, I think it's a bit of a problem /
challenge to fiddle these things out every time you wish to implement
TiddlyWeb... while sounding simply, user management / authentication /
registration workflows have their challenges
Hi Chris,
I'm happy to advise and support people, and do try to keep track of
anything that has some relevant to TiddlyWeb. However I don't want to
be in the position of initiating a repo as someone else doing so is a
clear sign of real commitment by someone or some group. I think it
On Monday, March 2, 2015 at 11:39:18 AM UTC+1, Tobias Beer wrote:
Mario mentioned that managing recipes, bags, even users may not entirely
be in the scope of the TiddlyWeb API.
You are right. not entirely. As Chris mentioned, there are several server
side plugins to manage users and access
On Mon, 2 Mar 2015, Tobias Beer wrote:
If that signal is lit, then woot, I'll watch closely.
Totally understand. So, let's wait and see some more when attempted
implementation(s) start trickling down.
It's probably not the most productive strategy but time being what it
is...
A
Hi Chris,
One reason user management workflows aren't built into TiddlyWeb is because
one size won't fit all.
I imagined the rationale would be something like that. So, taking a look at
*socialusers* for TiddlyWeb may prove to be the best approach to not start
all from scratch.
For
On Mon, 2 Mar 2015, Tobias Beer wrote:
I imagined the rationale would be something like that. So, taking a look at
*socialusers* for TiddlyWeb may prove to be the best approach to not start
all from scratch.
Yes, likely.
I take it, *tank *implements its own authentication layer / workflow /
On Fri, 20 Feb 2015, Tobias Beer wrote:
However, while you may not be equiped with the time-resources to do it all
yourself, I think you could perhaps keep an eye on vision /
implementation... being the most knowledgeable on the perhaps more critical
TiddlyWeb end. Let's face it, who else
9 matches
Mail list logo
