[tw] TiddlyServer backup and file ownership

[Glenn D]

I have this set up and running on my Raspberry Pi, but the backup feature
doesn't seem to work. I set backups to '/home/pi/backup' and have a
directory set up there, owned by pi:pi

I edited and saved a few tiddlers, but nothing shows up in the backup
folder.

I also rebooted the Pi, just to make sure the TiddlyServer was restarted.

After some further checking around, I notice that most of the system
tiddlers and several that I created myself are owned by pi:pi - but a lot
of other tiddlers that I created are owned by root:root

Why would that be?

[TonyM]

Glenn,

I don't have the full answer but the Tiddlers you update that are "served"
to you are written back to the server by the server, not you. If you use
the file save it is you saving the file.

I have created backup folders under all my Tiddlywikis that TiddlyServer
Serves, updated the settings.json to "backup" and I am not seeing it backup.

Regards
Tony

[Glenn D]

I've never used the 'file save' so we can rule that out.

I chmodded both backup and the onboot.sh to 777 - rebooted. I can see that
root is running npm, but not sure if that is the only process identifiable
for tiddlyserver...

I edit a tiddler, changes are autosaved, and still nothing in the backup
folder.

So everything works, but I am nervous about doing a lot more work without a
backup. Really not sure how to proceed at this point.

Post by TonyM
Glenn,
I don't have the full answer but the Tiddlers you update that are "served"
to you are written back to the server by the server, not you. If you use
the file save it is you saving the file.
I have created backup folders under all my Tiddlywikis that TiddlyServer
Serves, updated the settings.json to "backup" and I am not seeing it backup.
Regards
Tony

[Arlen Beiler]

Ok, two things to check.

1. Verify that the backup property in settings.json is a string with
characters. If it is a string with zero length, backups will not happen. If
it is a string with characters, an error will be thrown if the backup
cannot be saved. You will see a line in the terminal that lists a 500
status code as well as an extra error message.

2. Backups only apply to single file wikis, not data folders. If the wiki
is indicating that it got saved (i.e. the check mark turns grey) then it
should have saved. And if it did save, then the backup saved as well.

So check for errors in the terminal. Then see if your changes got saved.
Then make sure that the backup property actually specified a folder.

Hope that helps.
Arlen

Post by Glenn D
I've never used the 'file save' so we can rule that out.
I chmodded both backup and the onboot.sh to 777 - rebooted. I can see that
root is running npm, but not sure if that is the only process identifiable
for tiddlyserver...
I edit a tiddler, changes are autosaved, and still nothing in the backup
folder.
So everything works, but I am nervous about doing a lot more work without
a backup. Really not sure how to proceed at this point.

Post by TonyM
Glenn,
I don't have the full answer but the Tiddlers you update that are
"served" to you are written back to the server by the server, not you. If
you use the file save it is you saving the file.
I have created backup folders under all my Tiddlywikis that TiddlyServer
Serves, updated the settings.json to "backup" and I am not seeing it backup.
Regards
Tony

--
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
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/
msgid/tiddlywiki/8a8d82e1-3169-4429-a7a7-85bf3b6dc2d0%40googlegroups.com
<https://groups.google.com/d/msgid/tiddlywiki/8a8d82e1-3169-4429-a7a7-85bf3b6dc2d0%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.

[Arlen Beiler]

Backups and version history for data folders would need to be implemented
under TiddlyWiki itself, in the filesystem adapter.

Post by Arlen Beiler
Ok, two things to check.
1. Verify that the backup property in settings.json is a string with
characters. If it is a string with zero length, backups will not happen. If
it is a string with characters, an error will be thrown if the backup
cannot be saved. You will see a line in the terminal that lists a 500
status code as well as an extra error message.
2. Backups only apply to single file wikis, not data folders. If the wiki
is indicating that it got saved (i.e. the check mark turns grey) then it
should have saved. And if it did save, then the backup saved as well.
So check for errors in the terminal. Then see if your changes got saved.
Then make sure that the backup property actually specified a folder.
Hope that helps.
Arlen

Post by Glenn D
I've never used the 'file save' so we can rule that out.
I chmodded both backup and the onboot.sh to 777 - rebooted. I can see
that root is running npm, but not sure if that is the only process
identifiable for tiddlyserver...
I edit a tiddler, changes are autosaved, and still nothing in the backup
folder.
So everything works, but I am nervous about doing a lot more work without
a backup. Really not sure how to proceed at this point.

Post by TonyM
Glenn,
I don't have the full answer but the Tiddlers you update that are
"served" to you are written back to the server by the server, not you. If
you use the file save it is you saving the file.
I have created backup folders under all my Tiddlywikis that TiddlyServer
Serves, updated the settings.json to "backup" and I am not seeing it backup.
Regards
Tony

--
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
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/ms
gid/tiddlywiki/8a8d82e1-3169-4429-a7a7-85bf3b6dc2d0%40googlegroups.com
<https://groups.google.com/d/msgid/tiddlywiki/8a8d82e1-3169-4429-a7a7-85bf3b6dc2d0%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.

[RichardWilliamSmith]

Hi Glenn,

I'll look into this - I suspected there were some issues around ownership.
Did you follow the instructions I wrote? ie; do you have 'crontab' or
similar set up to restart the server on reboot? I'm wondering whether it
reboots into a different account... have you tried giving the backup folder
different permissions? Personally I'm ok with 'chmod 777'ing things when
they're on the Pi (I keep my secret plans for world domination elsewhere).
If that works, it might be simpler to install it as root in the first
place, for less overall faffing.

I'd be grateful if you could let us know what you figure out.

Regards,
Richard

Post by Glenn D
I have this set up and running on my Raspberry Pi, but the backup feature
doesn't seem to work. I set backups to '/home/pi/backup' and have a
directory set up there, owned by pi:pi
I edited and saved a few tiddlers, but nothing shows up in the backup
folder.
I also rebooted the Pi, just to make sure the TiddlyServer was restarted.
After some further checking around, I notice that most of the system
tiddlers and several that I created myself are owned by pi:pi - but a lot
of other tiddlers that I created are owned by root:root
Why would that be?

[Arlen Beiler]

The backup folder should be relative to settings.json. But it sounds like
you're using an absolute path, so that should work. One thing to try is to
run node in your terminal and type fs.statSync('backup path string copied
from settings.json') and see what it says. It could definitely be
ownership, let us know :)

On Sat, Oct 7, 2017 at 12:05 AM, RichardWilliamSmith <

Post by RichardWilliamSmith
Hi Glenn,
I'll look into this - I suspected there were some issues around ownership.
Did you follow the instructions I wrote? ie; do you have 'crontab' or
similar set up to restart the server on reboot? I'm wondering whether it
reboots into a different account... have you tried giving the backup folder
different permissions? Personally I'm ok with 'chmod 777'ing things when
they're on the Pi (I keep my secret plans for world domination elsewhere).
If that works, it might be simpler to install it as root in the first
place, for less overall faffing.
I'd be grateful if you could let us know what you figure out.
Regards,
Richard

Post by Glenn D
I have this set up and running on my Raspberry Pi, but the backup feature
doesn't seem to work. I set backups to '/home/pi/backup' and have a
directory set up there, owned by pi:pi
I edited and saved a few tiddlers, but nothing shows up in the backup
folder.
I also rebooted the Pi, just to make sure the TiddlyServer was restarted.
After some further checking around, I notice that most of the system
tiddlers and several that I created myself are owned by pi:pi - but a lot
of other tiddlers that I created are owned by root:root
Why would that be?

--
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
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/
msgid/tiddlywiki/5402cfb1-d595-4270-a3db-2d37efa4f016%40googlegroups.com
<https://groups.google.com/d/msgid/tiddlywiki/5402cfb1-d595-4270-a3db-2d37efa4f016%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.

[@TiddlyTweeter]

Ciao Arlen

In posts about TiddlyServer can you please DIFFERENTIATE the Simple Saving
Version (bundled) from the full node version?? Otherwise discussions will
get people like me in a confused knot.

Or maybe they should be given totally different names?

Best wishes
Josiah

[Arlen Beiler]

TiddlyServer is all the same. The only difference is whether it comes with
a node_modules folder (the -bundled.zip version) or whether you have to run
npm install yourself. And now the mac launcher version we are working on
will contain the bundled version + launcher code.

The backup folder only applies to single file TiddlyWikis, not TiddlyWiki
folders, since NodeJS TiddlyWiki doesn't currently have a backup feature
and TiddlyServer is using NodeJS TiddlyWiki for TiddlyWiki folders. But
they both run on TiddlyServer.

Am I understanding your question?

Arlen

Post by @TiddlyTweeter
Ciao Arlen
In posts about TiddlyServer can you please DIFFERENTIATE the Simple Saving
Version (bundled) from the full node version?? Otherwise discussions will
get people like me in a confused knot.
Or maybe they should be given totally different names?
Best wishes
Josiah
--
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
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/
msgid/tiddlywiki/d26a4562-8d87-4ee7-ae1c-432b2ec0cd6d%40googlegroups.com
<https://groups.google.com/d/msgid/tiddlywiki/d26a4562-8d87-4ee7-ae1c-432b2ec0cd6d%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.

[@TiddlyTweeter]

Ciao Arlen

I probably don't understand my own question :-).

The point is this ... FUNCTIONALLY I'm a user who downloaded the "Bundled"
(non-npm) version to be an alternative "TiddlyWiki-saver" to TiddlyFox.
Nothing more. And I had no idea it did more than that. IF it has additional
backup options then I'd need clearer documentation of that. I might use
them, though I backup using normal backup software.

I think the difficulty I am pointing at is neither directly mine nor yours.
Its in-between. Your coming from a great deal of knowledge and daily
practice. I'm coming from a place of only wanting to be able to seamlessly
save my TW.

Seamless saving by ONE product with ONE name that does ONE thing I think is
what makes it SO important right now. IF its also got other useful features
then that is good too BUT at a certain point when a newbie starts hitting
code you have to enter through the console it starts looking less simple
and gets confusing.

In other words: Have a dumb-version where you need know nothing else than
how to install it (which is not so easy for dumb people already :-) that is
targetted wholly at saving (only)?

Let's keep talking till both of use are clear what the other means, okay?

Best wishes
Josiah

['Mark S.' via TiddlyWiki]

I'm curious where you down-loaded from. At github, if you scroll down you
see the readme displayed, which details features like back-ups. Given, it's
not intuitive at all that you need to scroll down to see it.

Mark

Post by @TiddlyTweeter
Ciao Arlen
I probably don't understand my own question :-).
The point is this ... FUNCTIONALLY I'm a user who downloaded the "Bundled"
(non-npm) version to be an alternative "TiddlyWiki-saver" to TiddlyFox.
Nothing more. And I had no idea it did more than that. IF it has additional
backup options then I'd need clearer documentation of that. I might use
them, though I backup using normal backup software.
I think the difficulty I am pointing at is neither directly mine nor
yours. Its in-between. Your coming from a great deal of knowledge and daily
practice. I'm coming from a place of only wanting to be able to seamlessly
save my TW.
Seamless saving by ONE product with ONE name that does ONE thing I think
is what makes it SO important right now. IF its also got other useful
features then that is good too BUT at a certain point when a newbie starts
hitting code you have to enter through the console it starts looking less
simple and gets confusing.
In other words: Have a dumb-version where you need know nothing else than
how to install it (which is not so easy for dumb people already :-) that is
targetted wholly at saving (only)?
Let's keep talking till both of us are clear what the other means, okay?
Best wishes
Josiah

[@TiddlyTweeter]

Ciao Mark S.

This is a good example of me, the idiot, having an aim I want get done with
so I can get on writing (plays & stuff) and NOT have to deal with anything
more than I need to know to be certain my writing won't go down a computer
toilet.

Arlen has my apologies for my not paying attention. But I got working what
I needed.

At the same time I don't think I'm unusual. There is only so much idiots
need to know.

I'm convinced that TiddlyServer(Lite) is great for saving. A function thing
other things can't. I don't need to know it backs up--especially if that
involves much more than pushing a button. Backup I know about and do--there
are zillions of programs that do that already.

Do you kinda get my drift?

Best wishes
Josiah

Post by 'Mark S.' via TiddlyWiki
I'm curious where you down-loaded from. At github, if you scroll down you
see the readme displayed, which details features like back-ups. Given, it's
not intuitive at all that you need to scroll down to see it.
Mark

Post by @TiddlyTweeter
Ciao Arlen
I probably don't understand my own question :-).
The point is this ... FUNCTIONALLY I'm a user who downloaded the
"Bundled" (non-npm) version to be an alternative "TiddlyWiki-saver" to
TiddlyFox. Nothing more. And I had no idea it did more than that. IF it has
additional backup options then I'd need clearer documentation of that. I
might use them, though I backup using normal backup software.
I think the difficulty I am pointing at is neither directly mine nor
yours. Its in-between. Your coming from a great deal of knowledge and daily
practice. I'm coming from a place of only wanting to be able to seamlessly
save my TW.
Seamless saving by ONE product with ONE name that does ONE thing I think
is what makes it SO important right now. IF its also got other useful
features then that is good too BUT at a certain point when a newbie starts
hitting code you have to enter through the console it starts looking less
simple and gets confusing.
In other words: Have a dumb-version where you need know nothing else than
how to install it (which is not so easy for dumb people already :-) that is
targetted wholly at saving (only)?
Let's keep talking till both of us are clear what the other means, okay?
Best wishes
Josiah

[Arlen Beiler]

Post by @TiddlyTweeter
Do you kinda get my drift?

I think I am getting it. It's hard to know how to explain things for
developer DIYers (like me) and end-user DIYers both at the same time. And
then there are people with more important things to do :). But I see your
point.

When I published TiddlyServer, I did not foresee the discussion Firefox
would generate, nor the role TiddlyServer would play in that discussion. My
goal in making it was to make data folder wikis as flexible as single file
wikis, thus the emphasis on data folders.

I'll try to not overload people with technical details, except in technical
discussions such as this one.

Thanks,
Arlen

Post by @TiddlyTweeter
Ciao Mark S.
This is a good example of me, the idiot, having an aim I want get done
with so I can get on writing (plays & stuff) and NOT have to deal with
anything more than I need to know to be certain my writing won't go down a
computer toilet.
Arlen has my apologies for my not paying attention. But I got working
what I needed.
At the same time I don't think I'm unusual. There is only so much idiots
need to know.
I'm convinced that TiddlyServer(Lite) is great for saving. A function
thing other things can't. I don't need to know it backs up--especially if
that involves much more than pushing a button. Backup I know about and
do--there are zillions of programs that do that already.
Do you kinda get my drift?
Best wishes
Josiah

Post by 'Mark S.' via TiddlyWiki
I'm curious where you down-loaded from. At github, if you scroll down you
see the readme displayed, which details features like back-ups. Given, it's
not intuitive at all that you need to scroll down to see it.
Mark

Post by @TiddlyTweeter
Ciao Arlen
I probably don't understand my own question :-).
The point is this ... FUNCTIONALLY I'm a user who downloaded the
"Bundled" (non-npm) version to be an alternative "TiddlyWiki-saver" to
TiddlyFox. Nothing more. And I had no idea it did more than that. IF it has
additional backup options then I'd need clearer documentation of that. I
might use them, though I backup using normal backup software.
I think the difficulty I am pointing at is neither directly mine nor
yours. Its in-between. Your coming from a great deal of knowledge and daily
practice. I'm coming from a place of only wanting to be able to seamlessly
save my TW.
Seamless saving by ONE product with ONE name that does ONE thing I think
is what makes it SO important right now. IF its also got other useful
features then that is good too BUT at a certain point when a newbie starts
hitting code you have to enter through the console it starts looking less
simple and gets confusing.
In other words: Have a dumb-version where you need know nothing else
than how to install it (which is not so easy for dumb people already :-)
that is targetted wholly at saving (only)?
Let's keep talking till both of us are clear what the other means, okay?
Best wishes
Josiah

--

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
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/ms
gid/tiddlywiki/67e6d1c2-5fb0-4354-8815-eb0c7d36e540%40googlegroups.com
<https://groups.google.com/d/msgid/tiddlywiki/67e6d1c2-5fb0-4354-8815-eb0c7d36e540%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.

[@TiddlyTweeter]

Post by Arlen Beiler
I'll try to not overload people with technical details, except in
technical discussions such as this one.

Ciao Arlen

Just a footnote. It is NOT a problem for me witnessing technical
discussions. This is a group that needs them often, is good at them and
they are productive. Its in its nature.

My point is between a simple idiot's version of TiddlyServer("SaveOnly")
and the more elegant, full featured TiddlyServer.

Using the same name for both I do think can get confusing. EVEN IF the
"SaveOnly" version is, under the hood, the same thing as the other version.
Its a naming problem, I think. You think of ONE product. I think of TWO and
I don't need to know anything about the Other One as it gives me
complications I don't need.

I hope this is clearer?

Best wishes
Josiah

[Arlen Beiler]

Hi TiddlyTweeter,

Post by @TiddlyTweeter
The point is this ... FUNCTIONALLY I'm a user who downloaded the "Bundled"
(non-npm) version to be an alternative "TiddlyWiki-saver" to TiddlyFox.
Nothing more. And I had no idea it did more than that. IF it has additional
backup options then I'd need clearer documentation of that. I might use
them, though I backup using normal backup software.

Everything I've ever said about TiddlyServer applies equally to the
"Bundled" (non-npm) version and the "Source Code" (npm ) version *after you
run "npm install" on the npm version.*

"npm install" pulls in TiddlyWiki from NPM, whereas the bundled version
already has tiddlywiki from npm included.

If all you use it for is saving, that's fine. The NodeJS version of
TiddlyWiki, and thus TiddlyServer, has some useful features, but they are
not yet well documented. That was the whole point of making TiddlyServer,
was to allow NodeJS TiddlyWiki data folders (there are a couple examples in
editions) to be mounted, but it combined several other things that have
been requested on this GG as well, such as the ability to serve static
files alongside the TiddlyWiki server, and of course saving single-file
TiddlyWikis.

I am currently trying to make the configuration more user-friendly as well.
And yes, I do need better documentation :) I'm thankful for those of you
who have taken up the slack in figuring it out and helping others figure it
out, including your help @TiddlyTweeter.

If you want more information on using the NodeJS version of TiddlyWiki, you
can check out these links, but I digress. What TiddlyServer does is mount
TiddlyWiki Folders (aka data folders) at a path so they can be edited, just
like the server command. Under the hood, it actually uses the same code as
the server command.

- http://tiddlywiki.com/#TiddlyWiki%20on%20Node.js
- http://tiddlywiki.com/#ServerCommand
- http://tiddlywiki.com/#Installing%20TiddlyWiki%20on%20Node.js
- http://tiddlywiki.com/#TiddlyWikiFolders

Arlen

Post by @TiddlyTweeter
Ciao Arlen
I probably don't understand my own question :-).
The point is this ... FUNCTIONALLY I'm a user who downloaded the "Bundled"
(non-npm) version to be an alternative "TiddlyWiki-saver" to TiddlyFox.
Nothing more. And I had no idea it did more than that. IF it has additional
backup options then I'd need clearer documentation of that. I might use
them, though I backup using normal backup software.
I think the difficulty I am pointing at is neither directly mine nor
yours. Its in-between. Your coming from a great deal of knowledge and daily
practice. I'm coming from a place of only wanting to be able to seamlessly
save my TW.
Seamless saving by ONE product with ONE name that does ONE thing I think
is what makes it SO important right now. IF its also got other useful
features then that is good too BUT at a certain point when a newbie starts
hitting code you have to enter through the console it starts looking less
simple and gets confusing.
In other words: Have a dumb-version where you need know nothing else than
how to install it (which is not so easy for dumb people already :-) that is
targetted wholly at saving (only)?
Let's keep talking till both of use are clear what the other means, okay?
Best wishes
Josiah
--
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
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/
msgid/tiddlywiki/4827dc02-531e-44fa-9f10-bf3a346de96b%40googlegroups.com
<https://groups.google.com/d/msgid/tiddlywiki/4827dc02-531e-44fa-9f10-bf3a346de96b%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.

[@TiddlyTweeter]

Ciao Arlen

Its an interesting discussion.

The thing I want to underline is difference between the AIMS of different
kinds of users.

I do NOT find it a problem the whole thing it can potentially do IS
under-documented. Why? Because I'm not trying to do anything other than
use it to save. And previously we worked through many details of how to do
that here in GG. Its pretty clear now how to set it up (though maybe needs
bringing together & written up tighter sometime?).

When I have my "get-on-with-it" hat on (I have to get something written by
Thursday etc.) I'm NOT interested in anything other than being able to save
TW seamlessly--which TiddlyServer(Lite) does. And special because it DOES
THAT other things don't.

I already had auto-backup running for years so that addition adds nothing
practical for me.

I think my broader question is actually about what is the MOST MINIMAL
install needed to let you save TW? I.e. a VERSION as NARROW as possible for
that purpose.

I think your interest is about how to widen it up. Its that very liberal,
truly generous widening that I feel for idiots like me might be confusing.
And its around that that I find the naming confusing--many things start to
blur.

Best wishes
Josiah

Post by Arlen Beiler
Hi TiddlyTweeter,

Post by @TiddlyTweeter
The point is this ... FUNCTIONALLY I'm a user who downloaded the
"Bundled" (non-npm) version to be an alternative "TiddlyWiki-saver" to
TiddlyFox. Nothing more. And I had no idea it did more than that. IF it has
additional backup options then I'd need clearer documentation of that. I
might use them, though I backup using normal backup software.

Everything I've ever said about TiddlyServer applies equally to the
"Bundled" (non-npm) version and the "Source Code" (npm ) version *after
you run "npm install" on the npm version.*
"npm install" pulls in TiddlyWiki from NPM, whereas the bundled version
already has tiddlywiki from npm included.
If all you use it for is saving, that's fine. The NodeJS version of
TiddlyWiki, and thus TiddlyServer, has some useful features, but they are
not yet well documented. That was the whole point of making TiddlyServer,
was to allow NodeJS TiddlyWiki data folders (there are a couple examples in
editions) to be mounted, but it combined several other things that have
been requested on this GG as well, such as the ability to serve static
files alongside the TiddlyWiki server, and of course saving single-file
TiddlyWikis.
I am currently trying to make the configuration more user-friendly as
well. And yes, I do need better documentation :) I'm thankful for those of
you who have taken up the slack in figuring it out and helping others
If you want more information on using the NodeJS version of TiddlyWiki,
you can check out these links, but I digress. What TiddlyServer does is
mount TiddlyWiki Folders (aka data folders) at a path so they can be
edited, just like the server command. Under the hood, it actually uses the
same code as the server command.
- http://tiddlywiki.com/#TiddlyWiki%20on%20Node.js
- http://tiddlywiki.com/#ServerCommand
- http://tiddlywiki.com/#Installing%20TiddlyWiki%20on%20Node.js
- http://tiddlywiki.com/#TiddlyWikiFolders
Arlen

Post by @TiddlyTweeter
Ciao Arlen
I probably don't understand my own question :-).
The point is this ... FUNCTIONALLY I'm a user who downloaded the
"Bundled" (non-npm) version to be an alternative "TiddlyWiki-saver" to
TiddlyFox. Nothing more. And I had no idea it did more than that. IF it has
additional backup options then I'd need clearer documentation of that. I
might use them, though I backup using normal backup software.
I think the difficulty I am pointing at is neither directly mine nor
yours. Its in-between. Your coming from a great deal of knowledge and daily
practice. I'm coming from a place of only wanting to be able to seamlessly
save my TW.
Seamless saving by ONE product with ONE name that does ONE thing I think
is what makes it SO important right now. IF its also got other useful
features then that is good too BUT at a certain point when a newbie starts
hitting code you have to enter through the console it starts looking less
simple and gets confusing.
In other words: Have a dumb-version where you need know nothing else than
how to install it (which is not so easy for dumb people already :-) that is
targetted wholly at saving (only)?
Let's keep talking till both of use are clear what the other means, okay?
Best wishes
Josiah
--
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
<javascript:>.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/4827dc02-531e-44fa-9f10-bf3a346de96b%40googlegroups.com
<https://groups.google.com/d/msgid/tiddlywiki/4827dc02-531e-44fa-9f10-bf3a346de96b%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.

[TonyM]

Josiah,

To add to your observations and in no way detract, sometimes we need to
widen and make a solution more sophisticated, to make it simpler to use, It
is a balancing act that anyone who knows the details will have difficulty
understanding what it is to be a naive newbie. Perhaps we could recruit
newbies to be part of a documented install process.

Perhaps from TiddlyWIki.com

Regards
'Tony

Post by @TiddlyTweeter
Ciao Arlen
Its an interesting discussion.
The thing I want to underline is difference between the AIMS of different
kinds of users.
I do NOT find it a problem the whole thing it can potentially do IS
under-documented. Why? Because I'm not trying to do anything other than
use it to save. And previously we worked through many details of how to do
that here in GG. Its pretty clear now how to set it up (though maybe needs
bringing together & written up tighter sometime?).
When I have my "get-on-with-it" hat on (I have to get something written by
Thursday etc.) I'm NOT interested in anything other than being able to save
TW seamlessly--which TiddlyServer(Lite) does. And special because it DOES
THAT other things don't.
I already had auto-backup running for years so that addition adds nothing
practical for me.
I think my broader question is actually about what is the MOST MINIMAL
install needed to let you save TW? I.e. a VERSION as NARROW as possible for
that purpose.
I think your interest is about how to widen it up. Its that very liberal,
truly generous widening that I feel for idiots like me might be confusing.
And its around that that I find the naming confusing--many things start to
blur.
Best wishes
Josiah

Post by Arlen Beiler
Hi TiddlyTweeter,

Post by @TiddlyTweeter
The point is this ... FUNCTIONALLY I'm a user who downloaded the
"Bundled" (non-npm) version to be an alternative "TiddlyWiki-saver" to
TiddlyFox. Nothing more. And I had no idea it did more than that. IF it has
additional backup options then I'd need clearer documentation of that. I
might use them, though I backup using normal backup software.

Everything I've ever said about TiddlyServer applies equally to the
"Bundled" (non-npm) version and the "Source Code" (npm ) version *after
you run "npm install" on the npm version.*
"npm install" pulls in TiddlyWiki from NPM, whereas the bundled version
already has tiddlywiki from npm included.
If all you use it for is saving, that's fine. The NodeJS version of
TiddlyWiki, and thus TiddlyServer, has some useful features, but they are
not yet well documented. That was the whole point of making TiddlyServer,
was to allow NodeJS TiddlyWiki data folders (there are a couple examples in
editions) to be mounted, but it combined several other things that have
been requested on this GG as well, such as the ability to serve static
files alongside the TiddlyWiki server, and of course saving single-file
TiddlyWikis.
I am currently trying to make the configuration more user-friendly as
well. And yes, I do need better documentation :) I'm thankful for those of
you who have taken up the slack in figuring it out and helping others
If you want more information on using the NodeJS version of TiddlyWiki,
you can check out these links, but I digress. What TiddlyServer does is
mount TiddlyWiki Folders (aka data folders) at a path so they can be
edited, just like the server command. Under the hood, it actually uses the
same code as the server command.
- http://tiddlywiki.com/#TiddlyWiki%20on%20Node.js
- http://tiddlywiki.com/#ServerCommand
- http://tiddlywiki.com/#Installing%20TiddlyWiki%20on%20Node.js
- http://tiddlywiki.com/#TiddlyWikiFolders
Arlen

Post by @TiddlyTweeter
Ciao Arlen
I probably don't understand my own question :-).
The point is this ... FUNCTIONALLY I'm a user who downloaded the
"Bundled" (non-npm) version to be an alternative "TiddlyWiki-saver" to
TiddlyFox. Nothing more. And I had no idea it did more than that. IF it has
additional backup options then I'd need clearer documentation of that. I
might use them, though I backup using normal backup software.
I think the difficulty I am pointing at is neither directly mine nor
yours. Its in-between. Your coming from a great deal of knowledge and daily
practice. I'm coming from a place of only wanting to be able to seamlessly
save my TW.
Seamless saving by ONE product with ONE name that does ONE thing I think
is what makes it SO important right now. IF its also got other useful
features then that is good too BUT at a certain point when a newbie starts
hitting code you have to enter through the console it starts looking less
simple and gets confusing.
In other words: Have a dumb-version where you need know nothing else
than how to install it (which is not so easy for dumb people already :-)
that is targetted wholly at saving (only)?
Let's keep talking till both of use are clear what the other means, okay?
Best wishes
Josiah
--
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
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/4827dc02-531e-44fa-9f10-bf3a346de96b%40googlegroups.com
<https://groups.google.com/d/msgid/tiddlywiki/4827dc02-531e-44fa-9f10-bf3a346de96b%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.

[Glenn D]

Yes, i have crontab set up, although now that you mention it, I'm not sure
if it runs under root or pi. I'll check that.

Post by RichardWilliamSmith
Hi Glenn,
I'll look into this - I suspected there were some issues around ownership.
Did you follow the instructions I wrote? ie; do you have 'crontab' or
similar set up to restart the server on reboot? I'm wondering whether it
reboots into a different account... have you tried giving the backup folder
different permissions? Personally I'm ok with 'chmod 777'ing things when
they're on the Pi (I keep my secret plans for world domination elsewhere).
If that works, it might be simpler to install it as root in the first
place, for less overall faffing.
I'd be grateful if you could let us know what you figure out.
Regards,
Richard

Post by Glenn D
I have this set up and running on my Raspberry Pi, but the backup feature
doesn't seem to work. I set backups to '/home/pi/backup' and have a
directory set up there, owned by pi:pi
I edited and saved a few tiddlers, but nothing shows up in the backup
folder.
I also rebooted the Pi, just to make sure the TiddlyServer was restarted.
After some further checking around, I notice that most of the system
tiddlers and several that I created myself are owned by pi:pi - but a lot
of other tiddlers that I created are owned by root:root
Why would that be?