Well, it seems like no one really cares what happens to logging. It never was consistent anyway, since the data folder output still went to the console only. I think I'll just say if anyone runs into serious problems here feel free to open an issue on GitHub or email me here. Feel free to post if you didn't notice this thread before this.
Arlen On Tue, Apr 28, 2020 at 10:51 AM Arlen Beiler <arlen...@gmail.com> wrote: > Good morning everyone, > > As you may have noticed TiddlyServer 2.2 is now in the works, and the main > goals are making it simpler and easier to use. So my question is who all > uses the "logging" settings to log directly to a file. I'm planning to > remove this to keep things simpler. The recommended way to handle long > running processes is a process manager. I use PM2 on servers, and on > desktop I never log to file, so I'm curious if anyone would really miss > this feature if I removed it. > > I'm planning to print error messages to stderr and the startup messages > and regular access logs to stdout, instead of writing them to files, so you > can use redirection or other Node features to direct those streams to a > file. If this is a seriously missed feature I can add a couple ways to do > it but it seems like a rather complicated and niche feature, so I doubt > anyone uses it. > > Just thought I'd ask > 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/CAJ1vdSQKMf%2BjPr5MDwkDwxNJgQZJe%3DHhvKRo5UM0c51Grxigqw%40mail.gmail.com.
