Re: [tw5] Re: TiddlyServer upgraded to TiddlyWiki 5.1.21
So maybe I am missing something obvious but when I visit the above link or its home page https://arlen22.github.io/tiddlyserver/ I see no link to the actual current download location. You might want to include a Download section or a prominent link to https://github.com/Arlen22/TiddlyServer/releases/ in the Getting Started steps. Similarly with the README at https://github.com/Arlen22/TiddlyServer - where the Tiddlywiki site links. It does not seem apparent to this visitor where one goes to get the goods without finding the link in the original post above. -- 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/a9a6e858-dc8d-4bdc-afec-e2c360e70a06%40googlegroups.com.
Re: [tw5] Re: TiddlyServer upgraded to TiddlyWiki 5.1.21
I've add some JSON snippets to
https://arlen22.github.io/tiddlyserver/docs/serverconfig.html to hopefully
make it more clear what the entire configuration looks like.
On Fri, Oct 4, 2019 at 9:45 AM Arlen Beiler wrote:
> Mime types can now be added by specifying them under { "directoryIndex: {
> mimetypes: { "text/html": ["tw"] } } }
>
> On Fri, Oct 4, 2019 at 9:42 AM Arlen Beiler wrote:
>
>> export interface ServerConfig_TiddlyServer {
>> /**
>>
>>* Backup folder to store backups in. Multiple folder paths can backup to
>> the same folder if desired.
>>*/
>> backupFolder?: string,
>> /**
>>
>>* GZip backup file to save disk space. Good for larger wikis. Turn this
>> off for experimental wikis that you often need to restore from a backup
>> because of a bad line of code (I speak from experience).
>>*/
>> gzipBackups?: boolean,
>> /**
>>
>>* Reject an etag with a modified time that is different than the file on
>> disk by this many seconds.
>>
>>* Sometimes sync or antivirus sofware will "touch" a file and update the
>> modified time without changing anything.
>>* Size difference will still cause the request to be rejected.
>>*/
>> etagAge?: number,
>> /**
>>
>>* Whether to use the etag field -- if not specified then it will check it
>> if presented.
>>
>>* This does not affect the backup etagAge option, as the saving mechanism
>> will still
>>* send etags back to the browser, regardless of this option.
>>*/
>> etag?: "required" | "disabled" | "optional"
>> }
>>
>> On Fri, Oct 4, 2019 at 9:40 AM Arlen Beiler wrote:
>>
>>> The description on etagAge is not correct. It has nothing to do with
>>> backups. I'm not sure why I wrote that, but backups are always saved no
>>> matter what. I must have been tired that day!
>>>
>>> On Fri, Oct 4, 2019 at 9:37 AM Arlen Beiler wrote:
>>>
Here is the TypeScript interface for the putsaver property, which is a
top-level property (in other words, put it beside the tree property).
So
"putsaver": {
"backupFolder": "",
"etag": "optional",
// etc.
}
export interface ServerConfig_TiddlyServer {
/**
* Backup folder to store backups in. Multiple folder paths can backup
to the same folder if desired.
*/
backupFolder?: string,
/**
* GZip backup file to save disk space. Good for larger wikis. Turn this
off for experimental wikis that you often need to restore from a backup
because of a bad line of code (I speak from experience).
*/
gzipBackups?: boolean,
/**
* Save a backup only if the disk copy is older than this many seconds.
If the file on disk is only a few minutes old it can be assumed that very
little has changed since the last save. So if this is set to 10 minutes,
and your wiki gets saved every 9 minutes, only the first save will trigger
a backup. This is a useful option for large wikis that see a lot of daily
work but not useful for experimental wikis which might crash at any time
and need to be reloaded from the last backup.
*/
etagAge?: number,
/**
* Whether to use the etag field -- if not specified then it will check
it if presented.
* This does not affect the backup etagAge option, as the saving
mechanism will still
* send etags back to the browser, regardless of this option.
*/
etag?: "required" | "disabled" | "optional"
}
On Fri, Oct 4, 2019 at 9:11 AM Adrian Holbrook <
adrian.holbr...@gmail.com> wrote:
> Just out of curiosity as I have not been able to get the backup to
> work on the previous installation I notice that you have "backupDirectory"
> but in the Settinggs example files oin Version 2.1.3 it had
> "backupFolder".
> Is this important?
>
> Adrian
>
> On Friday, October 4, 2019 at 5:06:58 AM UTC+1, TonyM wrote:
>>
>> Arlen,
>>
>> Thanks for maintaining and enhancing this wonderful solution. I
>> notice the settings.json seems to have changed a lot. I copied my tree
>> into
>> the new settings.json
>>
>> But these settings were in my old settings.json
>> "types":{
>> "htmlfile": ["htm", "html", "hta", "png", "tw"]
>> },
>> "username": "",
>> "password": "",
>> "host": "192.168.1.81",
>> "port": 80,
>> "backupDirectory": "C:\\Data\\TW5\\backups",
>> "etagWindow": 10,
>> "etag": "",
>> "_disableLocalHost": "true",
>> "useTW5path" : false
>>
>> Have these being deprecated?
>>
>> I believe I will still need
>> "etag": "required",
>> "etagWindow": 10,
>>
>> But the setting the port is Port is not documented here
>>
Re: [tw5] Re: TiddlyServer upgraded to TiddlyWiki 5.1.21
Mime types can now be added by specifying them under { "directoryIndex: {
mimetypes: { "text/html": ["tw"] } } }
On Fri, Oct 4, 2019 at 9:42 AM Arlen Beiler wrote:
> export interface ServerConfig_TiddlyServer {
> /**
>
>* Backup folder to store backups in. Multiple folder paths can backup to
> the same folder if desired.
>*/
> backupFolder?: string,
> /**
>
>* GZip backup file to save disk space. Good for larger wikis. Turn this
> off for experimental wikis that you often need to restore from a backup
> because of a bad line of code (I speak from experience).
>*/
> gzipBackups?: boolean,
> /**
>
>* Reject an etag with a modified time that is different than the file on
> disk by this many seconds.
>
>* Sometimes sync or antivirus sofware will "touch" a file and update the
> modified time without changing anything.
>* Size difference will still cause the request to be rejected.
>*/
> etagAge?: number,
> /**
>
>* Whether to use the etag field -- if not specified then it will check it
> if presented.
>
>* This does not affect the backup etagAge option, as the saving mechanism
> will still
>* send etags back to the browser, regardless of this option.
>*/
> etag?: "required" | "disabled" | "optional"
> }
>
> On Fri, Oct 4, 2019 at 9:40 AM Arlen Beiler wrote:
>
>> The description on etagAge is not correct. It has nothing to do with
>> backups. I'm not sure why I wrote that, but backups are always saved no
>> matter what. I must have been tired that day!
>>
>> On Fri, Oct 4, 2019 at 9:37 AM Arlen Beiler wrote:
>>
>>> Here is the TypeScript interface for the putsaver property, which is a
>>> top-level property (in other words, put it beside the tree property).
>>>
>>> So
>>> "putsaver": {
>>> "backupFolder": "",
>>> "etag": "optional",
>>> // etc.
>>> }
>>>
>>> export interface ServerConfig_TiddlyServer {
>>> /**
>>>
>>>* Backup folder to store backups in. Multiple folder paths can backup to
>>> the same folder if desired.
>>>*/
>>> backupFolder?: string,
>>> /**
>>>
>>>* GZip backup file to save disk space. Good for larger wikis. Turn this
>>> off for experimental wikis that you often need to restore from a backup
>>> because of a bad line of code (I speak from experience).
>>>*/
>>> gzipBackups?: boolean,
>>> /**
>>>
>>>* Save a backup only if the disk copy is older than this many seconds.
>>> If the file on disk is only a few minutes old it can be assumed that very
>>> little has changed since the last save. So if this is set to 10 minutes,
>>> and your wiki gets saved every 9 minutes, only the first save will trigger
>>> a backup. This is a useful option for large wikis that see a lot of daily
>>> work but not useful for experimental wikis which might crash at any time
>>> and need to be reloaded from the last backup.
>>>*/
>>> etagAge?: number,
>>> /**
>>>
>>>* Whether to use the etag field -- if not specified then it will check
>>> it if presented.
>>>
>>>* This does not affect the backup etagAge option, as the saving
>>> mechanism will still
>>>* send etags back to the browser, regardless of this option.
>>>*/
>>> etag?: "required" | "disabled" | "optional"
>>> }
>>>
>>> On Fri, Oct 4, 2019 at 9:11 AM Adrian Holbrook <
>>> adrian.holbr...@gmail.com> wrote:
>>>
Just out of curiosity as I have not been able to get the backup to work
on the previous installation I notice that you have "backupDirectory" but
in the Settinggs example files oin Version 2.1.3 it had "backupFolder". Is
this important?
Adrian
On Friday, October 4, 2019 at 5:06:58 AM UTC+1, TonyM wrote:
>
> Arlen,
>
> Thanks for maintaining and enhancing this wonderful solution. I notice
> the settings.json seems to have changed a lot. I copied my tree into the
> new settings.json
>
> But these settings were in my old settings.json
> "types":{
> "htmlfile": ["htm", "html", "hta", "png", "tw"]
> },
> "username": "",
> "password": "",
> "host": "192.168.1.81",
> "port": 80,
> "backupDirectory": "C:\\Data\\TW5\\backups",
> "etagWindow": 10,
> "etag": "",
> "_disableLocalHost": "true",
> "useTW5path" : false
>
> Have these being deprecated?
>
> I believe I will still need
> "etag": "required",
> "etagWindow": 10,
>
> But the setting the port is Port is not documented here
> https://arlen22.github.io/tiddlyserver/docs/serverconfig.html#port-number
>
> And
> "types":{
> "htmlfile": ["htm", "html", "hta", "png", "tw"]
> },
>
> Is desirable because I now have .tw files.
>
> Please let me know!
>
> Thanks
> Tony
>
>
> On Friday, October 4, 2019 at 12:56:46 PM UTC+10, Arlen Beiler wrote:
>>
>> Hi everyone,
>>
>> I've upgraded
Re: [tw5] Re: TiddlyServer upgraded to TiddlyWiki 5.1.21
export interface ServerConfig_TiddlyServer {
/**
* Backup folder to store backups in. Multiple folder paths can
backup to the same folder if desired.
*/
backupFolder?: string,
/**
* GZip backup file to save disk space. Good for larger wikis. Turn
this off for experimental wikis that you often need to restore from a
backup because of a bad line of code (I speak from experience).
*/
gzipBackups?: boolean,
/**
* Reject an etag with a modified time that is different than the
file on disk by this many seconds.
* Sometimes sync or antivirus sofware will "touch" a file and
update the modified time without changing anything.
* Size difference will still cause the request to be rejected.
*/
etagAge?: number,
/**
* Whether to use the etag field -- if not specified then it will
check it if presented.
* This does not affect the backup etagAge option, as the saving
mechanism will still
* send etags back to the browser, regardless of this option.
*/
etag?: "required" | "disabled" | "optional"
}
On Fri, Oct 4, 2019 at 9:40 AM Arlen Beiler wrote:
> The description on etagAge is not correct. It has nothing to do with
> backups. I'm not sure why I wrote that, but backups are always saved no
> matter what. I must have been tired that day!
>
> On Fri, Oct 4, 2019 at 9:37 AM Arlen Beiler wrote:
>
>> Here is the TypeScript interface for the putsaver property, which is a
>> top-level property (in other words, put it beside the tree property).
>>
>> So
>> "putsaver": {
>> "backupFolder": "",
>> "etag": "optional",
>> // etc.
>> }
>>
>> export interface ServerConfig_TiddlyServer {
>> /**
>>
>>* Backup folder to store backups in. Multiple folder paths can backup to
>> the same folder if desired.
>>*/
>> backupFolder?: string,
>> /**
>>
>>* GZip backup file to save disk space. Good for larger wikis. Turn this
>> off for experimental wikis that you often need to restore from a backup
>> because of a bad line of code (I speak from experience).
>>*/
>> gzipBackups?: boolean,
>> /**
>>
>>* Save a backup only if the disk copy is older than this many seconds. If
>> the file on disk is only a few minutes old it can be assumed that very
>> little has changed since the last save. So if this is set to 10 minutes, and
>> your wiki gets saved every 9 minutes, only the first save will trigger a
>> backup. This is a useful option for large wikis that see a lot of daily work
>> but not useful for experimental wikis which might crash at any time and need
>> to be reloaded from the last backup.
>>*/
>> etagAge?: number,
>> /**
>>
>>* Whether to use the etag field -- if not specified then it will check it
>> if presented.
>>
>>* This does not affect the backup etagAge option, as the saving mechanism
>> will still
>>* send etags back to the browser, regardless of this option.
>>*/
>> etag?: "required" | "disabled" | "optional"
>> }
>>
>> On Fri, Oct 4, 2019 at 9:11 AM Adrian Holbrook
>> wrote:
>>
>>> Just out of curiosity as I have not been able to get the backup to work
>>> on the previous installation I notice that you have "backupDirectory" but
>>> in the Settinggs example files oin Version 2.1.3 it had "backupFolder". Is
>>> this important?
>>>
>>> Adrian
>>>
>>> On Friday, October 4, 2019 at 5:06:58 AM UTC+1, TonyM wrote:
Arlen,
Thanks for maintaining and enhancing this wonderful solution. I notice
the settings.json seems to have changed a lot. I copied my tree into the
new settings.json
But these settings were in my old settings.json
"types":{
"htmlfile": ["htm", "html", "hta", "png", "tw"]
},
"username": "",
"password": "",
"host": "192.168.1.81",
"port": 80,
"backupDirectory": "C:\\Data\\TW5\\backups",
"etagWindow": 10,
"etag": "",
"_disableLocalHost": "true",
"useTW5path" : false
Have these being deprecated?
I believe I will still need
"etag": "required",
"etagWindow": 10,
But the setting the port is Port is not documented here
https://arlen22.github.io/tiddlyserver/docs/serverconfig.html#port-number
And
"types":{
"htmlfile": ["htm", "html", "hta", "png", "tw"]
},
Is desirable because I now have .tw files.
Please let me know!
Thanks
Tony
On Friday, October 4, 2019 at 12:56:46 PM UTC+10, Arlen Beiler wrote:
>
> Hi everyone,
>
> I've upgraded TiddlyServer to TW5.1.21.
>
> This release also adds /assets/tiddlywiki which serves the tiddlywiki
> folder the server is using to mount data folders. It's mainly for
> convenience, but it has some really great use-cases such as loading
> plugins
> as external javascript instead of in the HTML file, which of course get
> cached across your entire site, not
Re: [tw5] Re: TiddlyServer upgraded to TiddlyWiki 5.1.21
The description on etagAge is not correct. It has nothing to do with
backups. I'm not sure why I wrote that, but backups are always saved no
matter what. I must have been tired that day!
On Fri, Oct 4, 2019 at 9:37 AM Arlen Beiler wrote:
> Here is the TypeScript interface for the putsaver property, which is a
> top-level property (in other words, put it beside the tree property).
>
> So
> "putsaver": {
> "backupFolder": "",
> "etag": "optional",
> // etc.
> }
>
> export interface ServerConfig_TiddlyServer {
> /**
>
>* Backup folder to store backups in. Multiple folder paths can backup to
> the same folder if desired.
>*/
> backupFolder?: string,
> /**
>
>* GZip backup file to save disk space. Good for larger wikis. Turn this
> off for experimental wikis that you often need to restore from a backup
> because of a bad line of code (I speak from experience).
>*/
> gzipBackups?: boolean,
> /**
>
>* Save a backup only if the disk copy is older than this many seconds. If
> the file on disk is only a few minutes old it can be assumed that very little
> has changed since the last save. So if this is set to 10 minutes, and your
> wiki gets saved every 9 minutes, only the first save will trigger a backup.
> This is a useful option for large wikis that see a lot of daily work but not
> useful for experimental wikis which might crash at any time and need to be
> reloaded from the last backup.
>*/
> etagAge?: number,
> /**
>
>* Whether to use the etag field -- if not specified then it will check it
> if presented.
>
>* This does not affect the backup etagAge option, as the saving mechanism
> will still
>* send etags back to the browser, regardless of this option.
>*/
> etag?: "required" | "disabled" | "optional"
> }
>
> On Fri, Oct 4, 2019 at 9:11 AM Adrian Holbrook
> wrote:
>
>> Just out of curiosity as I have not been able to get the backup to work
>> on the previous installation I notice that you have "backupDirectory" but
>> in the Settinggs example files oin Version 2.1.3 it had "backupFolder". Is
>> this important?
>>
>> Adrian
>>
>> On Friday, October 4, 2019 at 5:06:58 AM UTC+1, TonyM wrote:
>>>
>>> Arlen,
>>>
>>> Thanks for maintaining and enhancing this wonderful solution. I notice
>>> the settings.json seems to have changed a lot. I copied my tree into the
>>> new settings.json
>>>
>>> But these settings were in my old settings.json
>>> "types":{
>>> "htmlfile": ["htm", "html", "hta", "png", "tw"]
>>> },
>>> "username": "",
>>> "password": "",
>>> "host": "192.168.1.81",
>>> "port": 80,
>>> "backupDirectory": "C:\\Data\\TW5\\backups",
>>> "etagWindow": 10,
>>> "etag": "",
>>> "_disableLocalHost": "true",
>>> "useTW5path" : false
>>>
>>> Have these being deprecated?
>>>
>>> I believe I will still need
>>> "etag": "required",
>>> "etagWindow": 10,
>>>
>>> But the setting the port is Port is not documented here
>>> https://arlen22.github.io/tiddlyserver/docs/serverconfig.html#port-number
>>>
>>> And
>>> "types":{
>>> "htmlfile": ["htm", "html", "hta", "png", "tw"]
>>> },
>>>
>>> Is desirable because I now have .tw files.
>>>
>>> Please let me know!
>>>
>>> Thanks
>>> Tony
>>>
>>>
>>> On Friday, October 4, 2019 at 12:56:46 PM UTC+10, Arlen Beiler wrote:
Hi everyone,
I've upgraded TiddlyServer to TW5.1.21.
This release also adds /assets/tiddlywiki which serves the tiddlywiki
folder the server is using to mount data folders. It's mainly for
convenience, but it has some really great use-cases such as loading plugins
as external javascript instead of in the HTML file, which of course get
cached across your entire site, not just for that page.
https://github.com/Arlen22/TiddlyServer/releases/tag/v2.1.5
Enjoy
Arlen
>>> --
>> 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/0484ce6b-e4d4-43b6-b343-ac28515f1616%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/CAJ1vdSROzOShHK1aLKi0HPsAFt98TJZbQiQbkJTMEs6FF5UOdA%40mail.gmail.com.
Re: [tw5] Re: TiddlyServer upgraded to TiddlyWiki 5.1.21
Here is the TypeScript interface for the putsaver property, which is a
top-level property (in other words, put it beside the tree property).
So
"putsaver": {
"backupFolder": "",
"etag": "optional",
// etc.
}
export interface ServerConfig_TiddlyServer {
/**
* Backup folder to store backups in. Multiple folder paths can
backup to the same folder if desired.
*/
backupFolder?: string,
/**
* GZip backup file to save disk space. Good for larger wikis. Turn
this off for experimental wikis that you often need to restore from a
backup because of a bad line of code (I speak from experience).
*/
gzipBackups?: boolean,
/**
* Save a backup only if the disk copy is older than this many
seconds. If the file on disk is only a few minutes old it can be
assumed that very little has changed since the last save. So if this
is set to 10 minutes, and your wiki gets saved every 9 minutes, only
the first save will trigger a backup. This is a useful option for
large wikis that see a lot of daily work but not useful for
experimental wikis which might crash at any time and need to be
reloaded from the last backup.
*/
etagAge?: number,
/**
* Whether to use the etag field -- if not specified then it will
check it if presented.
* This does not affect the backup etagAge option, as the saving
mechanism will still
* send etags back to the browser, regardless of this option.
*/
etag?: "required" | "disabled" | "optional"
}
On Fri, Oct 4, 2019 at 9:11 AM Adrian Holbrook
wrote:
> Just out of curiosity as I have not been able to get the backup to work on
> the previous installation I notice that you have "backupDirectory" but in
> the Settinggs example files oin Version 2.1.3 it had "backupFolder". Is
> this important?
>
> Adrian
>
> On Friday, October 4, 2019 at 5:06:58 AM UTC+1, TonyM wrote:
>>
>> Arlen,
>>
>> Thanks for maintaining and enhancing this wonderful solution. I notice
>> the settings.json seems to have changed a lot. I copied my tree into the
>> new settings.json
>>
>> But these settings were in my old settings.json
>> "types":{
>> "htmlfile": ["htm", "html", "hta", "png", "tw"]
>> },
>> "username": "",
>> "password": "",
>> "host": "192.168.1.81",
>> "port": 80,
>> "backupDirectory": "C:\\Data\\TW5\\backups",
>> "etagWindow": 10,
>> "etag": "",
>> "_disableLocalHost": "true",
>> "useTW5path" : false
>>
>> Have these being deprecated?
>>
>> I believe I will still need
>> "etag": "required",
>> "etagWindow": 10,
>>
>> But the setting the port is Port is not documented here
>> https://arlen22.github.io/tiddlyserver/docs/serverconfig.html#port-number
>>
>> And
>> "types":{
>> "htmlfile": ["htm", "html", "hta", "png", "tw"]
>> },
>>
>> Is desirable because I now have .tw files.
>>
>> Please let me know!
>>
>> Thanks
>> Tony
>>
>>
>> On Friday, October 4, 2019 at 12:56:46 PM UTC+10, Arlen Beiler wrote:
>>>
>>> Hi everyone,
>>>
>>> I've upgraded TiddlyServer to TW5.1.21.
>>>
>>> This release also adds /assets/tiddlywiki which serves the tiddlywiki
>>> folder the server is using to mount data folders. It's mainly for
>>> convenience, but it has some really great use-cases such as loading plugins
>>> as external javascript instead of in the HTML file, which of course get
>>> cached across your entire site, not just for that page.
>>>
>>> https://github.com/Arlen22/TiddlyServer/releases/tag/v2.1.5
>>>
>>> Enjoy
>>> Arlen
>>>
>> --
> 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/0484ce6b-e4d4-43b6-b343-ac28515f1616%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/CAJ1vdSTeHf_XrxsgFrrxCXJaU1bLcu5i8eai1q_%3DO5UBRS7Lcw%40mail.gmail.com.
