Re: [tw5] Re: Local-First Storage, with backup to cloud (Github)

[Joshua Fontany]

You should investigate Danielo's "NoteSelf" adaptation if TW which I belive 
syncs to a PouchDB server.

Also - TW defines the Title field as primary key. When title "changes" TW is 
actually storing a new tiddler under the new Title and deletes the old copy.

Best,
-Joshua F

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/94bec829-79ad-495f-a8a8-2da295d584b5%40googlegroups.com.

Re: [tw5] Re: Local-First Storage, with backup to cloud (Github)

[TonyM]

Walt,

Using a automatically issues ID is wise in these circumstances, however I 
have done work of fixed serial numbers for tiddler so Personal Message me 
if you want to discuss.

I am not in favor of using such a large serial number as created date/time, 
however the date can be transferred to an independant field, then tested to 
ensure its unique, simply incrementing milliseconds until it is unique. 
Then you hide this field from edit. The problems come about when dragging 
and dropping tiddlers from other wikis, but a test for uniqueness can 
occurs again, unless we were to include a wikiname in the serial numbers.

I expect a database solution may assume an empty.html with the stored 
tiddlers anything added or overwritten. There is a real question however 
with tiddlers delivered via the database that are needed as the wiki loads. 

You may not know couchDB but Noteself implementing a database model and 
would inform you, perhaps even give you code examples. Two notable features 
are tiddler versions and the use of a local couchDB when PouchDB not 
available and before connected. A Design path is to build first to a 
browser internal Database, then look at connecting to an external Database. 
this could allow one Tiddlywiki to switch databases, or one database share 
multiple wikis.

Regards
Tony

On Friday, 1 May 2020 05:03:19 UTC+10, ludwa6 wrote:
>
> If there's any doubt about using the "Created" field, then the 
> auto-assigned integer always works for PK (most RDBMs do it that way by 
> default, in fact). 
>
> Meanwhile, i am playing with tiddly server, trying to get Github Saver to 
> work, with no joy as of yet.  Is this supposed to work, or does it work 
> only for single-file instances, i wonder?
>
>
> On Thursday, April 30, 2020 at 6:08:24 PM UTC+1, Mark S. wrote:
>>
>> I'm not sure the created field is never cleaned off. Like possibly during 
>> export/import procedures. Or when packed/unpacked from a plugin. 
>> Maybe use a separate id field just to be sure. 
>>
>> On Thursday, April 30, 2020 at 9:52:28 AM UTC-7, Arlen Beiler wrote:
>>>
>>> If I was doing that I would auto assign an integer primary key, but if 
>>> that's more work you could use the created timestamp. 
>>>
>>> On Thu, Apr 30, 2020 at 8:40 AM ludwa6 
>>>
 Arlen: storage in a RDBMS (requirement for this application i want to 
 develop[1]) requires a Primary Key that is both guaranteed unique AND 
 cannot be changed -but tiddler Title *can* be changed, so that is not a 
 good candidate, seems to me. The one element of this schema that appears 
 immutable to me is that "created" date/time stamp, which has 3 digits 
 beyond minutes (thousandths of a minute, perhaps?), so that is 
 fine-grained 
 enough to guarantee uniqueness, i guess. 

 [1] To explain: i need RDBMS storage for this particular application 
 because i need to correlate tiddlers with records in other tables of the 
 database that they are meant to document, or otherwise extend. This RDBMS 
 lies at the heart of a gateway that facilitates data I/O with a set remote 
 nodes for sensing & control of farm operations -initially a 
 climate-controlled greenhouse.  The data flowing between nodes in this 
 environment is structured as a rule, such that humans cannot mess with it. 
 Yet it is precisely those "messy" human inputs -e.g. observations, photos, 
 links, questions, etc.- that i aim to capture thru TiddlyWiki.  The real 
 power of this application will lie in its ability to corrrelate machine 
 data with user-generated data... And for that, i need both to be stored in 
 RDBMS (just in case you were wondering why :-)


 On Thursday, April 30, 2020 at 12:23:00 PM UTC+1, Arlen Beiler wrote:
>
> Those last lines are a mystery to me. I've never seen them before. 
> I'll check make sure I'm not missing anything. 
>
> The tiddler title is the primary key in Tiddly wiki. I don't really 
> think you would need to store it anywhere else though.
>
> Everything is in flux right now, but hopefully we'll have it mailed 
> down soon and then I'll be able to better recommend how to use a database 
> with this. But it certainly isn't required. 
>
> On Thu, Apr 30, 2020, 06:42 ludwa6  wrote:
>
>> Arlen: Putting your earlier instructions together with Mark's 
>> declaration of listener port, i *think* i've got he server running on my 
>> Pi 
>> server... But in fact i'm still confused about this.  
>>
>> The UI looks & seems to be performing pretty much like TiddlyWiki 
>> single-file version, except that default "Getting Started" tiddler asked 
>> me 
>> to make & save one, & confirm that it worked... So i did, and now i see 
>> it 
>> in the file system, inside 'MyNewWikiFolder/tiddlers/ , along with 
>> $_StoryList.tid .  I then created a 2nd tiddler, which appeared as a 2nd 

Re: [tw5] Re: Local-First Storage, with backup to cloud (Github)

['Mark S.' via TiddlyWiki]

AFAIK, the github saver is for single-file TW's. 

On Thursday, April 30, 2020 at 12:03:19 PM UTC-7, ludwa6 wrote:
>
> If there's any doubt about using the "Created" field, then the 
> auto-assigned integer always works for PK (most RDBMs do it that way by 
> default, in fact). 
>
> Meanwhile, i am playing with tiddly server, trying to get Github Saver to 
> work, with no joy as of yet.  Is this supposed to work, or does it work 
> only for single-file instances, i wonder?
>
>
> On Thursday, April 30, 2020 at 6:08:24 PM UTC+1, Mark S. wrote:
>>
>> I'm not sure the created field is never cleaned off. Like possibly during 
>> export/import procedures. Or when packed/unpacked from a plugin. 
>> Maybe use a separate id field just to be sure. 
>>
>> On Thursday, April 30, 2020 at 9:52:28 AM UTC-7, Arlen Beiler wrote:
>>>
>>> If I was doing that I would auto assign an integer primary key, but if 
>>> that's more work you could use the created timestamp. 
>>>
>>> On Thu, Apr 30, 2020 at 8:40 AM ludwa6 
>>>
 Arlen: storage in a RDBMS (requirement for this application i want to 
 develop[1]) requires a Primary Key that is both guaranteed unique AND 
 cannot be changed -but tiddler Title *can* be changed, so that is not a 
 good candidate, seems to me. The one element of this schema that appears 
 immutable to me is that "created" date/time stamp, which has 3 digits 
 beyond minutes (thousandths of a minute, perhaps?), so that is 
 fine-grained 
 enough to guarantee uniqueness, i guess. 

 [1] To explain: i need RDBMS storage for this particular application 
 because i need to correlate tiddlers with records in other tables of the 
 database that they are meant to document, or otherwise extend. This RDBMS 
 lies at the heart of a gateway that facilitates data I/O with a set remote 
 nodes for sensing & control of farm operations -initially a 
 climate-controlled greenhouse.  The data flowing between nodes in this 
 environment is structured as a rule, such that humans cannot mess with it. 
 Yet it is precisely those "messy" human inputs -e.g. observations, photos, 
 links, questions, etc.- that i aim to capture thru TiddlyWiki.  The real 
 power of this application will lie in its ability to corrrelate machine 
 data with user-generated data... And for that, i need both to be stored in 
 RDBMS (just in case you were wondering why :-)


 On Thursday, April 30, 2020 at 12:23:00 PM UTC+1, Arlen Beiler wrote:
>
> Those last lines are a mystery to me. I've never seen them before. 
> I'll check make sure I'm not missing anything. 
>
> The tiddler title is the primary key in Tiddly wiki. I don't really 
> think you would need to store it anywhere else though.
>
> Everything is in flux right now, but hopefully we'll have it mailed 
> down soon and then I'll be able to better recommend how to use a database 
> with this. But it certainly isn't required. 
>
> On Thu, Apr 30, 2020, 06:42 ludwa6  wrote:
>
>> Arlen: Putting your earlier instructions together with Mark's 
>> declaration of listener port, i *think* i've got he server running on my 
>> Pi 
>> server... But in fact i'm still confused about this.  
>>
>> The UI looks & seems to be performing pretty much like TiddlyWiki 
>> single-file version, except that default "Getting Started" tiddler asked 
>> me 
>> to make & save one, & confirm that it worked... So i did, and now i see 
>> it 
>> in the file system, inside 'MyNewWikiFolder/tiddlers/ , along with 
>> $_StoryList.tid .  I then created a 2nd tiddler, which appeared as a 2nd 
>> file in the same directory... So can i safely presume i've got tiddly 
>> server working as it should?
>>
>> Now looking at the schema of these files, it seems pretty simple, 
>> i.e.: 
>>
>>- created: (date/time stamp in mmddhhmm format, followed by a 
>>3-digit numeric)
>>- modified: (same format as above)
>>- tags: (if any, a horizontal list)
>>- title: (as declared)
>>- type: text/vnd.tiddlywiki
>>- (single line space, followed by...
>>- (full text of tiddler, followed by...
>>- (some 16 lines, blank except for '~' as initial character...
>>- >- [noeol] 7L, 132C  7,23  ALL
>>
>> That last line is most mysterious to me, as i don't know what those 
>> codes refer to, nor why there's so many spaces preceding the last 2 
>> strings. 
>>
>> Best candidate for Primary Key here, as far as i can see, would be 
>> the first attribute -the "created" date/time stamp- but i don't know how 
>> to 
>> turn these files into rows in the SQLite database where i want to store 
>> the 
>> data. From what Tony said, i gather it would involve building a sync 
>> module 
>> of some sort, but 

Re: [tw5] Re: Local-First Storage, with backup to cloud (Github)

[ludwa6]

If there's any doubt about using the "Created" field, then the 
auto-assigned integer always works for PK (most RDBMs do it that way by 
default, in fact). 

Meanwhile, i am playing with tiddly server, trying to get Github Saver to 
work, with no joy as of yet.  Is this supposed to work, or does it work 
only for single-file instances, i wonder?


On Thursday, April 30, 2020 at 6:08:24 PM UTC+1, Mark S. wrote:
>
> I'm not sure the created field is never cleaned off. Like possibly during 
> export/import procedures. Or when packed/unpacked from a plugin. 
> Maybe use a separate id field just to be sure. 
>
> On Thursday, April 30, 2020 at 9:52:28 AM UTC-7, Arlen Beiler wrote:
>>
>> If I was doing that I would auto assign an integer primary key, but if 
>> that's more work you could use the created timestamp. 
>>
>> On Thu, Apr 30, 2020 at 8:40 AM ludwa6 
>>
>>> Arlen: storage in a RDBMS (requirement for this application i want to 
>>> develop[1]) requires a Primary Key that is both guaranteed unique AND 
>>> cannot be changed -but tiddler Title *can* be changed, so that is not a 
>>> good candidate, seems to me. The one element of this schema that appears 
>>> immutable to me is that "created" date/time stamp, which has 3 digits 
>>> beyond minutes (thousandths of a minute, perhaps?), so that is fine-grained 
>>> enough to guarantee uniqueness, i guess. 
>>>
>>> [1] To explain: i need RDBMS storage for this particular application 
>>> because i need to correlate tiddlers with records in other tables of the 
>>> database that they are meant to document, or otherwise extend. This RDBMS 
>>> lies at the heart of a gateway that facilitates data I/O with a set remote 
>>> nodes for sensing & control of farm operations -initially a 
>>> climate-controlled greenhouse.  The data flowing between nodes in this 
>>> environment is structured as a rule, such that humans cannot mess with it. 
>>> Yet it is precisely those "messy" human inputs -e.g. observations, photos, 
>>> links, questions, etc.- that i aim to capture thru TiddlyWiki.  The real 
>>> power of this application will lie in its ability to corrrelate machine 
>>> data with user-generated data... And for that, i need both to be stored in 
>>> RDBMS (just in case you were wondering why :-)
>>>
>>>
>>> On Thursday, April 30, 2020 at 12:23:00 PM UTC+1, Arlen Beiler wrote:

 Those last lines are a mystery to me. I've never seen them before. I'll 
 check make sure I'm not missing anything. 

 The tiddler title is the primary key in Tiddly wiki. I don't really 
 think you would need to store it anywhere else though.

 Everything is in flux right now, but hopefully we'll have it mailed 
 down soon and then I'll be able to better recommend how to use a database 
 with this. But it certainly isn't required. 

 On Thu, Apr 30, 2020, 06:42 ludwa6  wrote:

> Arlen: Putting your earlier instructions together with Mark's 
> declaration of listener port, i *think* i've got he server running on my 
> Pi 
> server... But in fact i'm still confused about this.  
>
> The UI looks & seems to be performing pretty much like TiddlyWiki 
> single-file version, except that default "Getting Started" tiddler asked 
> me 
> to make & save one, & confirm that it worked... So i did, and now i see 
> it 
> in the file system, inside 'MyNewWikiFolder/tiddlers/ , along with 
> $_StoryList.tid .  I then created a 2nd tiddler, which appeared as a 2nd 
> file in the same directory... So can i safely presume i've got tiddly 
> server working as it should?
>
> Now looking at the schema of these files, it seems pretty simple, 
> i.e.: 
>
>- created: (date/time stamp in mmddhhmm format, followed by a 
>3-digit numeric)
>- modified: (same format as above)
>- tags: (if any, a horizontal list)
>- title: (as declared)
>- type: text/vnd.tiddlywiki
>- (single line space, followed by...
>- (full text of tiddler, followed by...
>- (some 16 lines, blank except for '~' as initial character...
>- - [noeol] 7L, 132C  7,23  ALL
>
> That last line is most mysterious to me, as i don't know what those 
> codes refer to, nor why there's so many spaces preceding the last 2 
> strings. 
>
> Best candidate for Primary Key here, as far as i can see, would be the 
> first attribute -the "created" date/time stamp- but i don't know how to 
> turn these files into rows in the SQLite database where i want to store 
> the 
> data. From what Tony said, i gather it would involve building a sync 
> module 
> of some sort, but i have no idea how that might be done.  Any prior art, 
> or 
> ideas about this?
>
>
>
> On Wednesday, April 29, 2020 at 7:00:25 PM UTC+1, Arlen Beiler wrote:
>>
>> Sorry, what I said was for tiddly 

Re: [tw5] Re: Local-First Storage, with backup to cloud (Github)

['Mark S.' via TiddlyWiki]

I'm not sure the created field is never cleaned off. Like possibly during 
export/import procedures. Or when packed/unpacked from a plugin. 
Maybe use a separate id field just to be sure. 

On Thursday, April 30, 2020 at 9:52:28 AM UTC-7, Arlen Beiler wrote:
>
> If I was doing that I would auto assign an integer primary key, but if 
> that's more work you could use the created timestamp. 
>
> On Thu, Apr 30, 2020 at 8:40 AM ludwa6 
>
>> Arlen: storage in a RDBMS (requirement for this application i want to 
>> develop[1]) requires a Primary Key that is both guaranteed unique AND 
>> cannot be changed -but tiddler Title *can* be changed, so that is not a 
>> good candidate, seems to me. The one element of this schema that appears 
>> immutable to me is that "created" date/time stamp, which has 3 digits 
>> beyond minutes (thousandths of a minute, perhaps?), so that is fine-grained 
>> enough to guarantee uniqueness, i guess. 
>>
>> [1] To explain: i need RDBMS storage for this particular application 
>> because i need to correlate tiddlers with records in other tables of the 
>> database that they are meant to document, or otherwise extend. This RDBMS 
>> lies at the heart of a gateway that facilitates data I/O with a set remote 
>> nodes for sensing & control of farm operations -initially a 
>> climate-controlled greenhouse.  The data flowing between nodes in this 
>> environment is structured as a rule, such that humans cannot mess with it. 
>> Yet it is precisely those "messy" human inputs -e.g. observations, photos, 
>> links, questions, etc.- that i aim to capture thru TiddlyWiki.  The real 
>> power of this application will lie in its ability to corrrelate machine 
>> data with user-generated data... And for that, i need both to be stored in 
>> RDBMS (just in case you were wondering why :-)
>>
>>
>> On Thursday, April 30, 2020 at 12:23:00 PM UTC+1, Arlen Beiler wrote:
>>>
>>> Those last lines are a mystery to me. I've never seen them before. I'll 
>>> check make sure I'm not missing anything. 
>>>
>>> The tiddler title is the primary key in Tiddly wiki. I don't really 
>>> think you would need to store it anywhere else though.
>>>
>>> Everything is in flux right now, but hopefully we'll have it mailed down 
>>> soon and then I'll be able to better recommend how to use a database with 
>>> this. But it certainly isn't required. 
>>>
>>> On Thu, Apr 30, 2020, 06:42 ludwa6  wrote:
>>>
 Arlen: Putting your earlier instructions together with Mark's 
 declaration of listener port, i *think* i've got he server running on my 
 Pi 
 server... But in fact i'm still confused about this.  

 The UI looks & seems to be performing pretty much like TiddlyWiki 
 single-file version, except that default "Getting Started" tiddler asked 
 me 
 to make & save one, & confirm that it worked... So i did, and now i see it 
 in the file system, inside 'MyNewWikiFolder/tiddlers/ , along with 
 $_StoryList.tid .  I then created a 2nd tiddler, which appeared as a 2nd 
 file in the same directory... So can i safely presume i've got tiddly 
 server working as it should?

 Now looking at the schema of these files, it seems pretty simple, i.e.: 

- created: (date/time stamp in mmddhhmm format, followed by a 
3-digit numeric)
- modified: (same format as above)
- tags: (if any, a horizontal list)
- title: (as declared)
- type: text/vnd.tiddlywiki
- (single line space, followed by...
- (full text of tiddler, followed by...
- (some 16 lines, blank except for '~' as initial character...
- >>>- [noeol] 7L, 132C  7,23  ALL

 That last line is most mysterious to me, as i don't know what those 
 codes refer to, nor why there's so many spaces preceding the last 2 
 strings. 

 Best candidate for Primary Key here, as far as i can see, would be the 
 first attribute -the "created" date/time stamp- but i don't know how to 
 turn these files into rows in the SQLite database where i want to store 
 the 
 data. From what Tony said, i gather it would involve building a sync 
 module 
 of some sort, but i have no idea how that might be done.  Any prior art, 
 or 
 ideas about this?



 On Wednesday, April 29, 2020 at 7:00:25 PM UTC+1, Arlen Beiler wrote:
>
> Sorry, what I said was for tiddly server. What mark said is for tiddly 
> wiki.
>
> On Wed, Apr 29, 2020, 13:56 'Mark S.' via TiddlyWiki <
> tiddl...@googlegroups.com> wrote:
>
>>
>> The listen command can take a port number. Like
>>
>> --listen port=8090
>>
>>
>> On Wednesday, April 29, 2020 at 9:37:36 AM UTC-7, ludwa6 wrote:
>>>
>>> Hey Arlen: Great to hear, thanks! 
>>> So i ran those commands, installed TiddlyServer on my Raspberry Pi 
>>> gateway... But hit a little snag setting up the 

Re: [tw5] Re: Local-First Storage, with backup to cloud (Github)

[Arlen Beiler]

If I was doing that I would auto assign an integer primary key, but if
that's more work you could use the created timestamp.

On Thu, Apr 30, 2020 at 8:40 AM ludwa6  wrote:

> Arlen: storage in a RDBMS (requirement for this application i want to
> develop[1]) requires a Primary Key that is both guaranteed unique AND
> cannot be changed -but tiddler Title *can* be changed, so that is not a
> good candidate, seems to me. The one element of this schema that appears
> immutable to me is that "created" date/time stamp, which has 3 digits
> beyond minutes (thousandths of a minute, perhaps?), so that is fine-grained
> enough to guarantee uniqueness, i guess.
>
> [1] To explain: i need RDBMS storage for this particular application
> because i need to correlate tiddlers with records in other tables of the
> database that they are meant to document, or otherwise extend. This RDBMS
> lies at the heart of a gateway that facilitates data I/O with a set remote
> nodes for sensing & control of farm operations -initially a
> climate-controlled greenhouse.  The data flowing between nodes in this
> environment is structured as a rule, such that humans cannot mess with it.
> Yet it is precisely those "messy" human inputs -e.g. observations, photos,
> links, questions, etc.- that i aim to capture thru TiddlyWiki.  The real
> power of this application will lie in its ability to corrrelate machine
> data with user-generated data... And for that, i need both to be stored in
> RDBMS (just in case you were wondering why :-)
>
>
> On Thursday, April 30, 2020 at 12:23:00 PM UTC+1, Arlen Beiler wrote:
>>
>> Those last lines are a mystery to me. I've never seen them before. I'll
>> check make sure I'm not missing anything.
>>
>> The tiddler title is the primary key in Tiddly wiki. I don't really think
>> you would need to store it anywhere else though.
>>
>> Everything is in flux right now, but hopefully we'll have it mailed down
>> soon and then I'll be able to better recommend how to use a database with
>> this. But it certainly isn't required.
>>
>> On Thu, Apr 30, 2020, 06:42 ludwa6  wrote:
>>
>>> Arlen: Putting your earlier instructions together with Mark's
>>> declaration of listener port, i *think* i've got he server running on my Pi
>>> server... But in fact i'm still confused about this.
>>>
>>> The UI looks & seems to be performing pretty much like TiddlyWiki
>>> single-file version, except that default "Getting Started" tiddler asked me
>>> to make & save one, & confirm that it worked... So i did, and now i see it
>>> in the file system, inside 'MyNewWikiFolder/tiddlers/ , along with
>>> $_StoryList.tid .  I then created a 2nd tiddler, which appeared as a 2nd
>>> file in the same directory... So can i safely presume i've got tiddly
>>> server working as it should?
>>>
>>> Now looking at the schema of these files, it seems pretty simple, i.e.:
>>>
>>>- created: (date/time stamp in mmddhhmm format, followed by a
>>>3-digit numeric)
>>>- modified: (same format as above)
>>>- tags: (if any, a horizontal list)
>>>- title: (as declared)
>>>- type: text/vnd.tiddlywiki
>>>- (single line space, followed by...
>>>- (full text of tiddler, followed by...
>>>- (some 16 lines, blank except for '~' as initial character...
>>>- >>- [noeol] 7L, 132C  7,23  ALL
>>>
>>> That last line is most mysterious to me, as i don't know what those
>>> codes refer to, nor why there's so many spaces preceding the last 2
>>> strings.
>>>
>>> Best candidate for Primary Key here, as far as i can see, would be the
>>> first attribute -the "created" date/time stamp- but i don't know how to
>>> turn these files into rows in the SQLite database where i want to store the
>>> data. From what Tony said, i gather it would involve building a sync module
>>> of some sort, but i have no idea how that might be done.  Any prior art, or
>>> ideas about this?
>>>
>>>
>>>
>>> On Wednesday, April 29, 2020 at 7:00:25 PM UTC+1, Arlen Beiler wrote:

 Sorry, what I said was for tiddly server. What mark said is for tiddly
 wiki.

 On Wed, Apr 29, 2020, 13:56 'Mark S.' via TiddlyWiki <
 tiddl...@googlegroups.com> wrote:

>
> The listen command can take a port number. Like
>
> --listen port=8090
>
>
> On Wednesday, April 29, 2020 at 9:37:36 AM UTC-7, ludwa6 wrote:
>>
>> Hey Arlen: Great to hear, thanks!
>> So i ran those commands, installed TiddlyServer on my Raspberry Pi
>> gateway... But hit a little snag setting up the listener, in that port
>> :8080 is owned by another application server.  Can't change that for the
>> moment, as it's a service i can't really mess with.  Could talk to that
>> developer about changing the port he's using, i suppose...
>>
>> But just to see this working, i tried to install on my Mac, but
>> terminal tells me:
>>
>> -bash: npm: command not found
>> Suppose i could use a different 

Re: [tw5] Re: Local-First Storage, with backup to cloud (Github)

[ludwa6]

Heh -looks like you are right, Mark: i was viewing text of tiddler in the 
terminal, but when i opened it in a text editor , it was simply this:

created: 20200430094059869
> modified: 20200430094129604
> tags: test
> title: FirstPost
> type: text/vnd.tiddlywiki
> What hath God wrought?


- and nothing more.  All that afterbirth in my previous msg in this thread 
was some irrelevant terminal screed, i guess But if this is all there 
is to a tiddler, it should be simple to store in SQLite, i imagine, for one 
who knows how to write a "Sync module" (wish i knew how!).  /w



On Thursday, April 30, 2020 at 2:23:57 PM UTC+1, Mark S. wrote:
>
>
>
> On Thursday, April 30, 2020 at 3:42:34 AM UTC-7, ludwa6 wrote:
>>
>>
>>- (some 16 lines, blank except for '~' as initial character...
>>- >- [noeol] 7L, 132C  7,23  ALL
>>
>>
>>
> Are you sure these aren't visual artefacts of  the editor you're using? 
> Some old editors display a tilde at the start of each blank line, and that 
> line on the bottom looks like an info display. Maybe you could post one of 
> the new tiddlers?
>
>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/17f75f81-e2bd-4833-95a3-b94c7058c378%40googlegroups.com.

Re: [tw5] Re: Local-First Storage, with backup to cloud (Github)

['Mark S.' via TiddlyWiki]

On Thursday, April 30, 2020 at 3:42:34 AM UTC-7, ludwa6 wrote:
>
>
>- (some 16 lines, blank except for '~' as initial character...
>- - [noeol] 7L, 132C  7,23  ALL
>
>
>
Are you sure these aren't visual artefacts of  the editor you're using? 
Some old editors display a tilde at the start of each blank line, and that 
line on the bottom looks like an info display. Maybe you could post one of 
the new tiddlers?


-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/6afcfbbc-d3da-4aba-a05c-a8d6e419%40googlegroups.com.

Re: [tw5] Re: Local-First Storage, with backup to cloud (Github)

[ludwa6]

Arlen: storage in a RDBMS (requirement for this application i want to 
develop[1]) requires a Primary Key that is both guaranteed unique AND 
cannot be changed -but tiddler Title *can* be changed, so that is not a 
good candidate, seems to me. The one element of this schema that appears 
immutable to me is that "created" date/time stamp, which has 3 digits 
beyond minutes (thousandths of a minute, perhaps?), so that is fine-grained 
enough to guarantee uniqueness, i guess. 

[1] To explain: i need RDBMS storage for this particular application 
because i need to correlate tiddlers with records in other tables of the 
database that they are meant to document, or otherwise extend. This RDBMS 
lies at the heart of a gateway that facilitates data I/O with a set remote 
nodes for sensing & control of farm operations -initially a 
climate-controlled greenhouse.  The data flowing between nodes in this 
environment is structured as a rule, such that humans cannot mess with it. 
Yet it is precisely those "messy" human inputs -e.g. observations, photos, 
links, questions, etc.- that i aim to capture thru TiddlyWiki.  The real 
power of this application will lie in its ability to corrrelate machine 
data with user-generated data... And for that, i need both to be stored in 
RDBMS (just in case you were wondering why :-)


On Thursday, April 30, 2020 at 12:23:00 PM UTC+1, Arlen Beiler wrote:
>
> Those last lines are a mystery to me. I've never seen them before. I'll 
> check make sure I'm not missing anything. 
>
> The tiddler title is the primary key in Tiddly wiki. I don't really think 
> you would need to store it anywhere else though.
>
> Everything is in flux right now, but hopefully we'll have it mailed down 
> soon and then I'll be able to better recommend how to use a database with 
> this. But it certainly isn't required. 
>
> On Thu, Apr 30, 2020, 06:42 ludwa6 > 
> wrote:
>
>> Arlen: Putting your earlier instructions together with Mark's declaration 
>> of listener port, i *think* i've got he server running on my Pi server... 
>> But in fact i'm still confused about this.  
>>
>> The UI looks & seems to be performing pretty much like TiddlyWiki 
>> single-file version, except that default "Getting Started" tiddler asked me 
>> to make & save one, & confirm that it worked... So i did, and now i see it 
>> in the file system, inside 'MyNewWikiFolder/tiddlers/ , along with 
>> $_StoryList.tid .  I then created a 2nd tiddler, which appeared as a 2nd 
>> file in the same directory... So can i safely presume i've got tiddly 
>> server working as it should?
>>
>> Now looking at the schema of these files, it seems pretty simple, i.e.: 
>>
>>- created: (date/time stamp in mmddhhmm format, followed by a 
>>3-digit numeric)
>>- modified: (same format as above)
>>- tags: (if any, a horizontal list)
>>- title: (as declared)
>>- type: text/vnd.tiddlywiki
>>- (single line space, followed by...
>>- (full text of tiddler, followed by...
>>- (some 16 lines, blank except for '~' as initial character...
>>- >- [noeol] 7L, 132C  7,23  ALL
>>
>> That last line is most mysterious to me, as i don't know what those codes 
>> refer to, nor why there's so many spaces preceding the last 2 strings. 
>>
>> Best candidate for Primary Key here, as far as i can see, would be the 
>> first attribute -the "created" date/time stamp- but i don't know how to 
>> turn these files into rows in the SQLite database where i want to store the 
>> data. From what Tony said, i gather it would involve building a sync module 
>> of some sort, but i have no idea how that might be done.  Any prior art, or 
>> ideas about this?
>>
>>
>>
>> On Wednesday, April 29, 2020 at 7:00:25 PM UTC+1, Arlen Beiler wrote:
>>>
>>> Sorry, what I said was for tiddly server. What mark said is for tiddly 
>>> wiki.
>>>
>>> On Wed, Apr 29, 2020, 13:56 'Mark S.' via TiddlyWiki <
>>> tiddl...@googlegroups.com> wrote:
>>>

 The listen command can take a port number. Like

 --listen port=8090


 On Wednesday, April 29, 2020 at 9:37:36 AM UTC-7, ludwa6 wrote:
>
> Hey Arlen: Great to hear, thanks! 
> So i ran those commands, installed TiddlyServer on my Raspberry Pi 
> gateway... But hit a little snag setting up the listener, in that port 
> :8080 is owned by another application server.  Can't change that for the 
> moment, as it's a service i can't really mess with.  Could talk to that 
> developer about changing the port he's using, i suppose...
>
> But just to see this working, i tried to install on my Mac, but 
> terminal tells me:
>
> -bash: npm: command not found
> Suppose i could use a different package manager, if i knew how (yes, i 
> am a complete unix n00b  =8-(
>
> Will try to bone up on the requisite skills, but any more crib notes 
> would of course be appreciated!
>
> /walt
>
>
> On Wednesday, April 

Re: [tw5] Re: Local-First Storage, with backup to cloud (Github)

[Arlen Beiler]

Yes, if they're properly showing up in the folder then everything is
working. Data folders are the second officially supported format in
tiddlywiki, after single file wikis. So feel free to just use the data
folder, in my opinion you don't need to store it anywhere else.

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSQ_DkPJnrZ0ZPvrq677_vcAfcqo1A6vM9WgPh5jGzXghw%40mail.gmail.com.

Re: [tw5] Re: Local-First Storage, with backup to cloud (Github)

[Arlen Beiler]

Those last lines are a mystery to me. I've never seen them before. I'll
check make sure I'm not missing anything.

The tiddler title is the primary key in Tiddly wiki. I don't really think
you would need to store it anywhere else though.

Everything is in flux right now, but hopefully we'll have it mailed down
soon and then I'll be able to better recommend how to use a database with
this. But it certainly isn't required.

On Thu, Apr 30, 2020, 06:42 ludwa6  wrote:

> Arlen: Putting your earlier instructions together with Mark's declaration
> of listener port, i *think* i've got he server running on my Pi server...
> But in fact i'm still confused about this.
>
> The UI looks & seems to be performing pretty much like TiddlyWiki
> single-file version, except that default "Getting Started" tiddler asked me
> to make & save one, & confirm that it worked... So i did, and now i see it
> in the file system, inside 'MyNewWikiFolder/tiddlers/ , along with
> $_StoryList.tid .  I then created a 2nd tiddler, which appeared as a 2nd
> file in the same directory... So can i safely presume i've got tiddly
> server working as it should?
>
> Now looking at the schema of these files, it seems pretty simple, i.e.:
>
>- created: (date/time stamp in mmddhhmm format, followed by a
>3-digit numeric)
>- modified: (same format as above)
>- tags: (if any, a horizontal list)
>- title: (as declared)
>- type: text/vnd.tiddlywiki
>- (single line space, followed by...
>- (full text of tiddler, followed by...
>- (some 16 lines, blank except for '~' as initial character...
>- - [noeol] 7L, 132C  7,23  ALL
>
> That last line is most mysterious to me, as i don't know what those codes
> refer to, nor why there's so many spaces preceding the last 2 strings.
>
> Best candidate for Primary Key here, as far as i can see, would be the
> first attribute -the "created" date/time stamp- but i don't know how to
> turn these files into rows in the SQLite database where i want to store the
> data. From what Tony said, i gather it would involve building a sync module
> of some sort, but i have no idea how that might be done.  Any prior art, or
> ideas about this?
>
>
>
> On Wednesday, April 29, 2020 at 7:00:25 PM UTC+1, Arlen Beiler wrote:
>>
>> Sorry, what I said was for tiddly server. What mark said is for tiddly
>> wiki.
>>
>> On Wed, Apr 29, 2020, 13:56 'Mark S.' via TiddlyWiki <
>> tiddl...@googlegroups.com> wrote:
>>
>>>
>>> The listen command can take a port number. Like
>>>
>>> --listen port=8090
>>>
>>>
>>> On Wednesday, April 29, 2020 at 9:37:36 AM UTC-7, ludwa6 wrote:

 Hey Arlen: Great to hear, thanks!
 So i ran those commands, installed TiddlyServer on my Raspberry Pi
 gateway... But hit a little snag setting up the listener, in that port
 :8080 is owned by another application server.  Can't change that for the
 moment, as it's a service i can't really mess with.  Could talk to that
 developer about changing the port he's using, i suppose...

 But just to see this working, i tried to install on my Mac, but
 terminal tells me:

 -bash: npm: command not found
 Suppose i could use a different package manager, if i knew how (yes, i
 am a complete unix n00b  =8-(

 Will try to bone up on the requisite skills, but any more crib notes
 would of course be appreciated!

 /walt


 On Wednesday, April 29, 2020 at 3:06:52 PM UTC+1, Arlen Beiler wrote:
>
> I have tried doing SQLite but there are some caveats that need to be
> accounted for.
>
> What I would recommend you do is use data folders instead of single
> file wikis. Data folders store tiddlers in individual text files using a
> custom format that Jeremy came up with. It works very well for text based
> storage solutions like GitHub. I'm actually really surprised no one
> mentioned this yet.
>
> To get started, install tiddlywiki globally by running npm install
> tiddlywiki -g
>
> Next, to create a blank data folder, run tiddlywiki ./MyNewWikiFolder
> --init server
>
> Then run tiddlywiki ./MyNewWikiFolder --listen
>
> Now open your browser to localhost:8080 and start exploring.
>
> TiddlyServer is a good way to load multiple data folders on the same
> port.
>
> Hope that helps,
> Arlen
>
> On Wed, Apr 29, 2020 at 7:52 AM ludwa6  wrote:
>
>> Such a wealth of options for Local-First storage have emerged in this
>> thread (must say: i'm super impressed with the strength of this 
>> community i
>> have just joined), i've been able to quickly implement the simple 
>> approach
>> suggested by Jeremy (TW Desktop, + cloud sync to Github), which is 
>> serving
>> me well enough for now.
>>
>> Yet, as i'm fast creating quite a mountain of data in TW, i'm also
>> bothered by the growing sense that what i 

Re: [tw5] Re: Local-First Storage, with backup to cloud (Github)

[ludwa6]

Arlen: Putting your earlier instructions together with Mark's declaration 
of listener port, i *think* i've got he server running on my Pi server... 
But in fact i'm still confused about this.  

The UI looks & seems to be performing pretty much like TiddlyWiki 
single-file version, except that default "Getting Started" tiddler asked me 
to make & save one, & confirm that it worked... So i did, and now i see it 
in the file system, inside 'MyNewWikiFolder/tiddlers/ , along with 
$_StoryList.tid .  I then created a 2nd tiddler, which appeared as a 2nd 
file in the same directory... So can i safely presume i've got tiddly 
server working as it should?

Now looking at the schema of these files, it seems pretty simple, i.e.: 

   - created: (date/time stamp in mmddhhmm format, followed by a 
   3-digit numeric)
   - modified: (same format as above)
   - tags: (if any, a horizontal list)
   - title: (as declared)
   - type: text/vnd.tiddlywiki
   - (single line space, followed by...
   - (full text of tiddler, followed by...
   - (some 16 lines, blank except for '~' as initial character...
   - 
> Sorry, what I said was for tiddly server. What mark said is for tiddly 
> wiki.
>
> On Wed, Apr 29, 2020, 13:56 'Mark S.' via TiddlyWiki <
> tiddl...@googlegroups.com > wrote:
>
>>
>> The listen command can take a port number. Like
>>
>> --listen port=8090
>>
>>
>> On Wednesday, April 29, 2020 at 9:37:36 AM UTC-7, ludwa6 wrote:
>>>
>>> Hey Arlen: Great to hear, thanks! 
>>> So i ran those commands, installed TiddlyServer on my Raspberry Pi 
>>> gateway... But hit a little snag setting up the listener, in that port 
>>> :8080 is owned by another application server.  Can't change that for the 
>>> moment, as it's a service i can't really mess with.  Could talk to that 
>>> developer about changing the port he's using, i suppose...
>>>
>>> But just to see this working, i tried to install on my Mac, but terminal 
>>> tells me:
>>>
>>> -bash: npm: command not found
>>> Suppose i could use a different package manager, if i knew how (yes, i 
>>> am a complete unix n00b  =8-(
>>>
>>> Will try to bone up on the requisite skills, but any more crib notes 
>>> would of course be appreciated!
>>>
>>> /walt
>>>
>>>
>>> On Wednesday, April 29, 2020 at 3:06:52 PM UTC+1, Arlen Beiler wrote:

 I have tried doing SQLite but there are some caveats that need to be 
 accounted for. 

 What I would recommend you do is use data folders instead of single 
 file wikis. Data folders store tiddlers in individual text files using a 
 custom format that Jeremy came up with. It works very well for text based 
 storage solutions like GitHub. I'm actually really surprised no one 
 mentioned this yet. 

 To get started, install tiddlywiki globally by running npm install 
 tiddlywiki -g

 Next, to create a blank data folder, run tiddlywiki ./MyNewWikiFolder 
 --init server

 Then run tiddlywiki ./MyNewWikiFolder --listen

 Now open your browser to localhost:8080 and start exploring. 

 TiddlyServer is a good way to load multiple data folders on the same 
 port. 

 Hope that helps, 
 Arlen

 On Wed, Apr 29, 2020 at 7:52 AM ludwa6  wrote:

> Such a wealth of options for Local-First storage have emerged in this 
> thread (must say: i'm super impressed with the strength of this community 
> i 
> have just joined), i've been able to quickly implement the simple 
> approach 
> suggested by Jeremy (TW Desktop, + cloud sync to Github), which is 
> serving 
> me well enough for now. 
>
> Yet, as i'm fast creating quite a mountain of data in TW, i'm also 
> bothered by the growing sense that what i really want at the back end of 
> this beautiful thing is a database -ideally SQLite, which has all that 
> local-first/ single-file/ portability goodness of TW, while bringing the 
> full set of functionalities needed to manage a large database with 
> integrity.  With a single SQLite file stored locally and replicated to 
> the 
> cloud, that gives us a solution that ticks all the boxes in that 
> seminal Local-First paper 
> : Fast, Multi-Device, 
> Offline, Collaboration, Longevity, Privacy, User-Control.  Combining this 
> with the power of TW5 interface (really an "interface builder for the 
> rest 
> of us," i would call it), minus mess of .html backup files i've got to 
> keep 
> cleaning off my machine (SQLite has a full transactional history, so no 
> need of any backups but that one file, replicated to cloud), and that in 
> broad-strokes would be the shape of my dream machine. 
>
> So i must ask: has anyone tried using SQLite as storage for a 
> TiddlyWiki?  If this is indeed technically feasible, can anyone point me 
> to 
> prior art on which i might be able to build 

Re: [tw5] Re: Local-First Storage, with backup to cloud (Github)

[ludwa6]

YES!  that worked, got 'er working on my R-Pi server now.  Thanks Mark!
/w

On Wednesday, April 29, 2020 at 6:56:45 PM UTC+1, Mark S. wrote:
>
>
> The listen command can take a port number. Like
>
> --listen port=8090
>
>
> On Wednesday, April 29, 2020 at 9:37:36 AM UTC-7, ludwa6 wrote:
>>
>> Hey Arlen: Great to hear, thanks! 
>> So i ran those commands, installed TiddlyServer on my Raspberry Pi 
>> gateway... But hit a little snag setting up the listener, in that port 
>> :8080 is owned by another application server.  Can't change that for the 
>> moment, as it's a service i can't really mess with.  Could talk to that 
>> developer about changing the port he's using, i suppose...
>>
>> But just to see this working, i tried to install on my Mac, but terminal 
>> tells me:
>>
>> -bash: npm: command not found
>> Suppose i could use a different package manager, if i knew how (yes, i am 
>> a complete unix n00b  =8-(
>>
>> Will try to bone up on the requisite skills, but any more crib notes 
>> would of course be appreciated!
>>
>> /walt
>>
>>
>> On Wednesday, April 29, 2020 at 3:06:52 PM UTC+1, Arlen Beiler wrote:
>>>
>>> I have tried doing SQLite but there are some caveats that need to be 
>>> accounted for. 
>>>
>>> What I would recommend you do is use data folders instead of single file 
>>> wikis. Data folders store tiddlers in individual text files using a custom 
>>> format that Jeremy came up with. It works very well for text based storage 
>>> solutions like GitHub. I'm actually really surprised no one mentioned this 
>>> yet. 
>>>
>>> To get started, install tiddlywiki globally by running npm install 
>>> tiddlywiki -g
>>>
>>> Next, to create a blank data folder, run tiddlywiki ./MyNewWikiFolder 
>>> --init server
>>>
>>> Then run tiddlywiki ./MyNewWikiFolder --listen
>>>
>>> Now open your browser to localhost:8080 and start exploring. 
>>>
>>> TiddlyServer is a good way to load multiple data folders on the same 
>>> port. 
>>>
>>> Hope that helps, 
>>> Arlen
>>>
>>> On Wed, Apr 29, 2020 at 7:52 AM ludwa6  wrote:
>>>
 Such a wealth of options for Local-First storage have emerged in this 
 thread (must say: i'm super impressed with the strength of this community 
 i 
 have just joined), i've been able to quickly implement the simple approach 
 suggested by Jeremy (TW Desktop, + cloud sync to Github), which is serving 
 me well enough for now. 

 Yet, as i'm fast creating quite a mountain of data in TW, i'm also 
 bothered by the growing sense that what i really want at the back end of 
 this beautiful thing is a database -ideally SQLite, which has all that 
 local-first/ single-file/ portability goodness of TW, while bringing the 
 full set of functionalities needed to manage a large database with 
 integrity.  With a single SQLite file stored locally and replicated to the 
 cloud, that gives us a solution that ticks all the boxes in that 
 seminal Local-First paper 
 : Fast, Multi-Device, 
 Offline, Collaboration, Longevity, Privacy, User-Control.  Combining this 
 with the power of TW5 interface (really an "interface builder for the rest 
 of us," i would call it), minus mess of .html backup files i've got to 
 keep 
 cleaning off my machine (SQLite has a full transactional history, so no 
 need of any backups but that one file, replicated to cloud), and that in 
 broad-strokes would be the shape of my dream machine. 

 So i must ask: has anyone tried using SQLite as storage for a 
 TiddlyWiki?  If this is indeed technically feasible, can anyone point me 
 to 
 prior art on which i might be able to build such a solution?  Though i am 
 no programmer, i am reasonably comfortable with SQL as a data manipulation 
 language, if someone can just show me how to get the TW data in there!

 -- 
 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 tiddl...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/tiddlywiki/856ad777-dc63-4491-bd74-c0391c4bf413%40googlegroups.com
  
 
 .

>>>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/adee29ea-4a78-4dbf-90f7-53306f6752c2%40googlegroups.com.

Re: [tw5] Re: Local-First Storage, with backup to cloud (Github)

[Arlen Beiler]

Sorry, what I said was for tiddly server. What mark said is for tiddly wiki.

On Wed, Apr 29, 2020, 13:56 'Mark S.' via TiddlyWiki <
tiddlywiki@googlegroups.com> wrote:

>
> The listen command can take a port number. Like
>
> --listen port=8090
>
>
> On Wednesday, April 29, 2020 at 9:37:36 AM UTC-7, ludwa6 wrote:
>>
>> Hey Arlen: Great to hear, thanks!
>> So i ran those commands, installed TiddlyServer on my Raspberry Pi
>> gateway... But hit a little snag setting up the listener, in that port
>> :8080 is owned by another application server.  Can't change that for the
>> moment, as it's a service i can't really mess with.  Could talk to that
>> developer about changing the port he's using, i suppose...
>>
>> But just to see this working, i tried to install on my Mac, but terminal
>> tells me:
>>
>> -bash: npm: command not found
>> Suppose i could use a different package manager, if i knew how (yes, i am
>> a complete unix n00b  =8-(
>>
>> Will try to bone up on the requisite skills, but any more crib notes
>> would of course be appreciated!
>>
>> /walt
>>
>>
>> On Wednesday, April 29, 2020 at 3:06:52 PM UTC+1, Arlen Beiler wrote:
>>>
>>> I have tried doing SQLite but there are some caveats that need to be
>>> accounted for.
>>>
>>> What I would recommend you do is use data folders instead of single file
>>> wikis. Data folders store tiddlers in individual text files using a custom
>>> format that Jeremy came up with. It works very well for text based storage
>>> solutions like GitHub. I'm actually really surprised no one mentioned this
>>> yet.
>>>
>>> To get started, install tiddlywiki globally by running npm install
>>> tiddlywiki -g
>>>
>>> Next, to create a blank data folder, run tiddlywiki ./MyNewWikiFolder
>>> --init server
>>>
>>> Then run tiddlywiki ./MyNewWikiFolder --listen
>>>
>>> Now open your browser to localhost:8080 and start exploring.
>>>
>>> TiddlyServer is a good way to load multiple data folders on the same
>>> port.
>>>
>>> Hope that helps,
>>> Arlen
>>>
>>> On Wed, Apr 29, 2020 at 7:52 AM ludwa6  wrote:
>>>
 Such a wealth of options for Local-First storage have emerged in this
 thread (must say: i'm super impressed with the strength of this community i
 have just joined), i've been able to quickly implement the simple approach
 suggested by Jeremy (TW Desktop, + cloud sync to Github), which is serving
 me well enough for now.

 Yet, as i'm fast creating quite a mountain of data in TW, i'm also
 bothered by the growing sense that what i really want at the back end of
 this beautiful thing is a database -ideally SQLite, which has all that
 local-first/ single-file/ portability goodness of TW, while bringing the
 full set of functionalities needed to manage a large database with
 integrity.  With a single SQLite file stored locally and replicated to the
 cloud, that gives us a solution that ticks all the boxes in that
 seminal Local-First paper
 : Fast, Multi-Device,
 Offline, Collaboration, Longevity, Privacy, User-Control.  Combining this
 with the power of TW5 interface (really an "interface builder for the rest
 of us," i would call it), minus mess of .html backup files i've got to keep
 cleaning off my machine (SQLite has a full transactional history, so no
 need of any backups but that one file, replicated to cloud), and that in
 broad-strokes would be the shape of my dream machine.

 So i must ask: has anyone tried using SQLite as storage for a
 TiddlyWiki?  If this is indeed technically feasible, can anyone point me to
 prior art on which i might be able to build such a solution?  Though i am
 no programmer, i am reasonably comfortable with SQL as a data manipulation
 language, if someone can just show me how to get the TW data in there!

 --
 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 tiddl...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/tiddlywiki/856ad777-dc63-4491-bd74-c0391c4bf413%40googlegroups.com
 
 .

>>> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/9571530e-806f-4a61-ae2f-ef1498d49f7b%40googlegroups.com
> 
> .
>

-- 
You received this message because you are 

Re: [tw5] Re: Local-First Storage, with backup to cloud (Github)

[Arlen Beiler]

I'm not at my computer right now, but you can specify the port in the
config file.

{ "bindInfo":{port:8090}}

On Wed, Apr 29, 2020, 12:37 ludwa6  wrote:

> Hey Arlen: Great to hear, thanks!
> So i ran those commands, installed TiddlyServer on my Raspberry Pi
> gateway... But hit a little snag setting up the listener, in that port
> :8080 is owned by another application server.  Can't change that for the
> moment, as it's a service i can't really mess with.  Could talk to that
> developer about changing the port he's using, i suppose...
>
> But just to see this working, i tried to install on my Mac, but terminal
> tells me:
>
> -bash: npm: command not found
> Suppose i could use a different package manager, if i knew how (yes, i am
> a complete unix n00b  =8-(
>
> Will try to bone up on the requisite skills, but any more crib notes would
> of course be appreciated!
>
> /walt
>
>
> On Wednesday, April 29, 2020 at 3:06:52 PM UTC+1, Arlen Beiler wrote:
>>
>> I have tried doing SQLite but there are some caveats that need to be
>> accounted for.
>>
>> What I would recommend you do is use data folders instead of single file
>> wikis. Data folders store tiddlers in individual text files using a custom
>> format that Jeremy came up with. It works very well for text based storage
>> solutions like GitHub. I'm actually really surprised no one mentioned this
>> yet.
>>
>> To get started, install tiddlywiki globally by running npm install
>> tiddlywiki -g
>>
>> Next, to create a blank data folder, run tiddlywiki ./MyNewWikiFolder
>> --init server
>>
>> Then run tiddlywiki ./MyNewWikiFolder --listen
>>
>> Now open your browser to localhost:8080 and start exploring.
>>
>> TiddlyServer is a good way to load multiple data folders on the same
>> port.
>>
>> Hope that helps,
>> Arlen
>>
>> On Wed, Apr 29, 2020 at 7:52 AM ludwa6  wrote:
>>
>>> Such a wealth of options for Local-First storage have emerged in this
>>> thread (must say: i'm super impressed with the strength of this community i
>>> have just joined), i've been able to quickly implement the simple approach
>>> suggested by Jeremy (TW Desktop, + cloud sync to Github), which is serving
>>> me well enough for now.
>>>
>>> Yet, as i'm fast creating quite a mountain of data in TW, i'm also
>>> bothered by the growing sense that what i really want at the back end of
>>> this beautiful thing is a database -ideally SQLite, which has all that
>>> local-first/ single-file/ portability goodness of TW, while bringing the
>>> full set of functionalities needed to manage a large database with
>>> integrity.  With a single SQLite file stored locally and replicated to the
>>> cloud, that gives us a solution that ticks all the boxes in that
>>> seminal Local-First paper
>>> : Fast, Multi-Device,
>>> Offline, Collaboration, Longevity, Privacy, User-Control.  Combining this
>>> with the power of TW5 interface (really an "interface builder for the rest
>>> of us," i would call it), minus mess of .html backup files i've got to keep
>>> cleaning off my machine (SQLite has a full transactional history, so no
>>> need of any backups but that one file, replicated to cloud), and that in
>>> broad-strokes would be the shape of my dream machine.
>>>
>>> So i must ask: has anyone tried using SQLite as storage for a
>>> TiddlyWiki?  If this is indeed technically feasible, can anyone point me to
>>> prior art on which i might be able to build such a solution?  Though i am
>>> no programmer, i am reasonably comfortable with SQL as a data manipulation
>>> language, if someone can just show me how to get the TW data in there!
>>>
>>> --
>>> 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 tiddl...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/tiddlywiki/856ad777-dc63-4491-bd74-c0391c4bf413%40googlegroups.com
>>> 
>>> .
>>>
>> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/ae0debc5-de0e-4b2a-8e94-7c7915a868dc%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Re: [tw5] Re: Local-First Storage, with backup to cloud (Github)

['Mark S.' via TiddlyWiki]

The listen command can take a port number. Like

--listen port=8090


On Wednesday, April 29, 2020 at 9:37:36 AM UTC-7, ludwa6 wrote:
>
> Hey Arlen: Great to hear, thanks! 
> So i ran those commands, installed TiddlyServer on my Raspberry Pi 
> gateway... But hit a little snag setting up the listener, in that port 
> :8080 is owned by another application server.  Can't change that for the 
> moment, as it's a service i can't really mess with.  Could talk to that 
> developer about changing the port he's using, i suppose...
>
> But just to see this working, i tried to install on my Mac, but terminal 
> tells me:
>
> -bash: npm: command not found
> Suppose i could use a different package manager, if i knew how (yes, i am 
> a complete unix n00b  =8-(
>
> Will try to bone up on the requisite skills, but any more crib notes would 
> of course be appreciated!
>
> /walt
>
>
> On Wednesday, April 29, 2020 at 3:06:52 PM UTC+1, Arlen Beiler wrote:
>>
>> I have tried doing SQLite but there are some caveats that need to be 
>> accounted for. 
>>
>> What I would recommend you do is use data folders instead of single file 
>> wikis. Data folders store tiddlers in individual text files using a custom 
>> format that Jeremy came up with. It works very well for text based storage 
>> solutions like GitHub. I'm actually really surprised no one mentioned this 
>> yet. 
>>
>> To get started, install tiddlywiki globally by running npm install 
>> tiddlywiki -g
>>
>> Next, to create a blank data folder, run tiddlywiki ./MyNewWikiFolder 
>> --init server
>>
>> Then run tiddlywiki ./MyNewWikiFolder --listen
>>
>> Now open your browser to localhost:8080 and start exploring. 
>>
>> TiddlyServer is a good way to load multiple data folders on the same 
>> port. 
>>
>> Hope that helps, 
>> Arlen
>>
>> On Wed, Apr 29, 2020 at 7:52 AM ludwa6  wrote:
>>
>>> Such a wealth of options for Local-First storage have emerged in this 
>>> thread (must say: i'm super impressed with the strength of this community i 
>>> have just joined), i've been able to quickly implement the simple approach 
>>> suggested by Jeremy (TW Desktop, + cloud sync to Github), which is serving 
>>> me well enough for now. 
>>>
>>> Yet, as i'm fast creating quite a mountain of data in TW, i'm also 
>>> bothered by the growing sense that what i really want at the back end of 
>>> this beautiful thing is a database -ideally SQLite, which has all that 
>>> local-first/ single-file/ portability goodness of TW, while bringing the 
>>> full set of functionalities needed to manage a large database with 
>>> integrity.  With a single SQLite file stored locally and replicated to the 
>>> cloud, that gives us a solution that ticks all the boxes in that 
>>> seminal Local-First paper 
>>> : Fast, Multi-Device, 
>>> Offline, Collaboration, Longevity, Privacy, User-Control.  Combining this 
>>> with the power of TW5 interface (really an "interface builder for the rest 
>>> of us," i would call it), minus mess of .html backup files i've got to keep 
>>> cleaning off my machine (SQLite has a full transactional history, so no 
>>> need of any backups but that one file, replicated to cloud), and that in 
>>> broad-strokes would be the shape of my dream machine. 
>>>
>>> So i must ask: has anyone tried using SQLite as storage for a 
>>> TiddlyWiki?  If this is indeed technically feasible, can anyone point me to 
>>> prior art on which i might be able to build such a solution?  Though i am 
>>> no programmer, i am reasonably comfortable with SQL as a data manipulation 
>>> language, if someone can just show me how to get the TW data in there!
>>>
>>> -- 
>>> 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 tiddl...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/tiddlywiki/856ad777-dc63-4491-bd74-c0391c4bf413%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/9571530e-806f-4a61-ae2f-ef1498d49f7b%40googlegroups.com.

Re: [tw5] Re: Local-First Storage, with backup to cloud (Github)

[ludwa6]

Hey Arlen: Great to hear, thanks! 
So i ran those commands, installed TiddlyServer on my Raspberry Pi 
gateway... But hit a little snag setting up the listener, in that port 
:8080 is owned by another application server.  Can't change that for the 
moment, as it's a service i can't really mess with.  Could talk to that 
developer about changing the port he's using, i suppose...

But just to see this working, i tried to install on my Mac, but terminal 
tells me:

-bash: npm: command not found
Suppose i could use a different package manager, if i knew how (yes, i am a 
complete unix n00b  =8-(

Will try to bone up on the requisite skills, but any more crib notes would 
of course be appreciated!

/walt


On Wednesday, April 29, 2020 at 3:06:52 PM UTC+1, Arlen Beiler wrote:
>
> I have tried doing SQLite but there are some caveats that need to be 
> accounted for. 
>
> What I would recommend you do is use data folders instead of single file 
> wikis. Data folders store tiddlers in individual text files using a custom 
> format that Jeremy came up with. It works very well for text based storage 
> solutions like GitHub. I'm actually really surprised no one mentioned this 
> yet. 
>
> To get started, install tiddlywiki globally by running npm install 
> tiddlywiki -g
>
> Next, to create a blank data folder, run tiddlywiki ./MyNewWikiFolder 
> --init server
>
> Then run tiddlywiki ./MyNewWikiFolder --listen
>
> Now open your browser to localhost:8080 and start exploring. 
>
> TiddlyServer is a good way to load multiple data folders on the same port. 
>
> Hope that helps, 
> Arlen
>
> On Wed, Apr 29, 2020 at 7:52 AM ludwa6 > 
> wrote:
>
>> Such a wealth of options for Local-First storage have emerged in this 
>> thread (must say: i'm super impressed with the strength of this community i 
>> have just joined), i've been able to quickly implement the simple approach 
>> suggested by Jeremy (TW Desktop, + cloud sync to Github), which is serving 
>> me well enough for now. 
>>
>> Yet, as i'm fast creating quite a mountain of data in TW, i'm also 
>> bothered by the growing sense that what i really want at the back end of 
>> this beautiful thing is a database -ideally SQLite, which has all that 
>> local-first/ single-file/ portability goodness of TW, while bringing the 
>> full set of functionalities needed to manage a large database with 
>> integrity.  With a single SQLite file stored locally and replicated to the 
>> cloud, that gives us a solution that ticks all the boxes in that seminal 
>> Local-First paper : Fast, 
>> Multi-Device, Offline, Collaboration, Longevity, Privacy, User-Control.  
>> Combining this with the power of TW5 interface (really an "interface 
>> builder for the rest of us," i would call it), minus mess of .html backup 
>> files i've got to keep cleaning off my machine (SQLite has a full 
>> transactional history, so no need of any backups but that one file, 
>> replicated to cloud), and that in broad-strokes would be the shape of my 
>> dream machine. 
>>
>> So i must ask: has anyone tried using SQLite as storage for a 
>> TiddlyWiki?  If this is indeed technically feasible, can anyone point me to 
>> prior art on which i might be able to build such a solution?  Though i am 
>> no programmer, i am reasonably comfortable with SQL as a data manipulation 
>> language, if someone can just show me how to get the TW data in there!
>>
>> -- 
>> 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 tiddl...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/856ad777-dc63-4491-bd74-c0391c4bf413%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/ae0debc5-de0e-4b2a-8e94-7c7915a868dc%40googlegroups.com.

Re: [tw5] Re: Local-First Storage, with backup to cloud (Github)

[Arlen Beiler]

I believe Tony is referring to the fact that a browser session is quickly
lost, including the unsaved data, once the user switches to a different app
on mobile devices. The only workaround that I know of would be to store
unsaved changes in local storage until they get synced. Which is basically
what noteself did.

So many different pieces of the puzzle. I often wish I could put them
together.

On Wed, Apr 29, 2020 at 9:03 AM Jed Carty  wrote:

> ludwa6,
>
> There have been a few database-backends made for tiddlywiki, I don't
> remember if anyone made a sqlite one or not, but it wouldn't be too hard
> and there are some examples around for it. I considered it for bob but I
> don't like sqlite, so I didn't use it.
>
> Tony,
>
> There is some misunderstanding here somewhere. I am completely lost. What
> is 'such a bob wiki' in this context? It acts like any other html wiki in
> the browser, it just has a plugin. I don't know what is new here or how
> being treated the same by the browser as an html wiki is something special.
>
> What works with the single file bob saver?
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/3f477a13-6892-491c-9498-21e54ce68e2f%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSRSL3hcahds0cz_3p%2BWmkUTRaWkQJuxWizrU3PjD9azww%40mail.gmail.com.

Re: [tw5] Re: Local-First Storage, with backup to cloud (Github)

[Arlen Beiler]

I have tried doing SQLite but there are some caveats that need to be
accounted for.

What I would recommend you do is use data folders instead of single file
wikis. Data folders store tiddlers in individual text files using a custom
format that Jeremy came up with. It works very well for text based storage
solutions like GitHub. I'm actually really surprised no one mentioned this
yet.

To get started, install tiddlywiki globally by running npm install
tiddlywiki -g

Next, to create a blank data folder, run tiddlywiki ./MyNewWikiFolder
--init server

Then run tiddlywiki ./MyNewWikiFolder --listen

Now open your browser to localhost:8080 and start exploring.

TiddlyServer is a good way to load multiple data folders on the same port.

Hope that helps,
Arlen

On Wed, Apr 29, 2020 at 7:52 AM ludwa6  wrote:

> Such a wealth of options for Local-First storage have emerged in this
> thread (must say: i'm super impressed with the strength of this community i
> have just joined), i've been able to quickly implement the simple approach
> suggested by Jeremy (TW Desktop, + cloud sync to Github), which is serving
> me well enough for now.
>
> Yet, as i'm fast creating quite a mountain of data in TW, i'm also
> bothered by the growing sense that what i really want at the back end of
> this beautiful thing is a database -ideally SQLite, which has all that
> local-first/ single-file/ portability goodness of TW, while bringing the
> full set of functionalities needed to manage a large database with
> integrity.  With a single SQLite file stored locally and replicated to the
> cloud, that gives us a solution that ticks all the boxes in that seminal
> Local-First paper : Fast,
> Multi-Device, Offline, Collaboration, Longevity, Privacy, User-Control.
> Combining this with the power of TW5 interface (really an "interface
> builder for the rest of us," i would call it), minus mess of .html backup
> files i've got to keep cleaning off my machine (SQLite has a full
> transactional history, so no need of any backups but that one file,
> replicated to cloud), and that in broad-strokes would be the shape of my
> dream machine.
>
> So i must ask: has anyone tried using SQLite as storage for a TiddlyWiki?
> If this is indeed technically feasible, can anyone point me to prior art on
> which i might be able to build such a solution?  Though i am no programmer,
> i am reasonably comfortable with SQL as a data manipulation language, if
> someone can just show me how to get the TW data in there!
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/856ad777-dc63-4491-bd74-c0391c4bf413%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdST-_8Lp6Q9TDGwKGG0NXw7JT9xbAKwm0ANOAzpMOSbcJQ%40mail.gmail.com.