RE: start-appserver view output on Windows

adamb940 — Sat, 10 Nov 2018 02:09:30 GMT

Thanks, I tried this PowerShell command and it worked. I am not sure why it works, because the file size still does not appear to change, but as it does work, I agree it's a better solution than using a custom batch file.

RE: start-appserver view output on Windows

josep — Sun, 04 Nov 2018 16:13:25 GMT

Hello Adam,

This is a good proposal, but going with this solution means each release we need to update it, what about a hot fix? I think it might happen the same. I think this sharing is good and I encourage you to continue finding solutions like this and sharing. There is always learning for all of us.

I will share you my thoughts on this.

The reason for this to happen is that the OS/logger has a buffer after certain size it flushes the file, so at the end it does it but maybe not when you need it or the way you want it. Here I have few options I have used.

Option 1) there are implementations of the Unix commands for windows. On which you will have the tail command Linux like. (Cygwin, mobaxterm, to give some examples)

Option 2) Have you tried the tail option from the PowerShell?
* Get-Content filepath -Wait -Tail 30
docs.microsoft.com/.../get-content

Option 3) if you open the file in a program let’s say notepad++ it detects when the file changes and ask you to reload it. The problem with this approach is that the file could be really big. But I pick this approach when I need to read the file and understand the errors Or when the log have reached the section I wanted.

Jose