CommaVee - Latest Comments

Re: AJAX Logfile Tailer & Viewer

John Minnihan — Wed, 12 Aug 2015 13:02:00 -0000

The source for Ajax Logfile Viewer is here:

https://dev.modernrepo.com/...

Use the 'Download zip' link in the top right of the page.

Re: AJAX Logfile Tailer & Viewer

adib — Mon, 10 Aug 2015 12:01:42 -0000

Could you zip a folder with the project working and send the link for download? Thanks

Re: AJAX Logfile Tailer & Viewer

adib — Mon, 10 Aug 2015 12:01:17 -0000

please, Could you zip a folder with the projetc working and send the link for download? Thanks

Re: AJAX Logfile Tailer & Viewer

thisisbazz — Tue, 08 Apr 2014 04:05:08 -0000

I LOVE IT!

Re: AJAX Logfile Tailer & Viewer

John Minnihan — Fri, 06 Dec 2013 20:50:37 -0000

Check http://dev1.modernrepo.com/...

Re: AJAX Logfile Tailer & Viewer

VICTOR MIRANDA — Wed, 04 Dec 2013 19:56:15 -0000

I am very new with AJAX and I don't know how to handle with all those files. Could you zip a folder with the projetc working and send the link for download? Thanks

Re: Using Node.js on Digital Ocean

DigitalOcean — Tue, 11 Jun 2013 13:26:38 -0000

Much thanks for that and glad to hear that you're liking our services. We already are appreciative of you trying us out and telling your thoughts to your community. Will be looking forward to your next upcoming post!

Re: Using Node.js on Digital Ocean

John Minnihan — Thu, 06 Jun 2013 14:03:53 -0000

Thanks. Definitely looking forward to new features.

I've been impressed w/ DO's responsiveness to my email inquires, so I'll have no prob recco'ing you folks.

Re: Using Node.js on Digital Ocean

DigitalOcean — Thu, 06 Jun 2013 12:57:44 -0000

Thank you so much for your detailed tutorial on installing and hosting
node.js with our servers! Really glad to see that you were able to have
it properly setup with ease. Additionally, we appreciate your honest assessment of our service. Do know that we are constantly iterating on a day by day basis which includes adding more features, improving our service quality, and increasing the reliability of our cloud servers.

Re: AJAX Logfile Tailer & Viewer

John Minnihan — Fri, 31 May 2013 08:54:33 -0000

I'd step back and rethink what you're trying to accomplish.

If you just need an up-to-date copy of a log file somewhere on disk, why not handle that inside the config of whatever system is generating the logfile? Just add another logger or whatever.

Re: AJAX Logfile Tailer & Viewer

MAC Man — Fri, 31 May 2013 05:50:41 -0000

I've been looking at this : https://github.com/ukhas/js...
Not as nice as your solution, but I like the idea it only updates the page with the differences in the file between each check, and doesn't use tail.
Could your script make use of that ?

Re: AJAX Logfile Tailer & Viewer

MAC Man — Thu, 30 May 2013 10:40:06 -0000

Thanks. I use foreach($output as $outputline) { to loop through the tail results and then that is echo'd back to my DIV. I also fwrite it to the log file.
I think that may be an issue with tail return the same lines if the log hasn't updated. using tail -n 100 returns the last 100 lines, regardless of the log file updating.
Not sure how to get around that..

Re: AJAX Logfile Tailer & Viewer

John Minnihan — Thu, 30 May 2013 10:30:44 -0000

If you are successfully writing lines to the new log file but are writing the same line over + over, this means that you aren't exiting the loop (assuming a foreach or similar) to obtain a new line of data before writing it to the new log file.

Wherever you are grabbing the next line of output + setting it to a var for the subsequent write, ensure that that var gets updated (refreshed with a real new line of log data) again before you write it to the new file. This likely means you'll move your write operation out of that 'foreach' or however you have implemented it.

Re: AJAX Logfile Tailer & Viewer

MAC Man — Thu, 30 May 2013 06:15:09 -0000

I've got this working and it works well. I've added : fwrite($f,$outputline."\n"); which writes the output to a new log file.
The issue I have is I end up with multiple lines the same. Any way to stop that from happening ?

Re: Using Node.js, Express, Socket.io and Exec

Zach Goldsmith — Tue, 21 May 2013 13:23:03 -0000

I think what I'm trying to do is out of the scope of the io.connections.emit ('relay'){'connections': Object.keys(io.connected).length }; function. I'm not really sure how to create the array of inbound msg.pageUrl. Even though I can trigger the counter, not sure how to "untrigger" the counter. The (msg.connections) would have to match the served .html string, and then create the $('#idtag.fromPageUrl').html(msg.connections) There would have to be a static entry to the code to delegate to proper counter, unless the delegation can be inferred as a regular <h1></h1> to describe the counter and creating the id="pageUrl" from the same string. This would be optimal to not have to static enter each .html page in code.

The .html pages will be accessed individually from an embed on another website, and not through a 'onhashchange' landing index/home.html page of the node client.

I can work around not having this feature, as I can essentially create several node instances bound to different ports, and then embed a results page into a master page from each node instance. Even though this will be a huge pain, and of course not scale-able.

Re: Using Node.js, Express, Socket.io and Exec

Zach Goldsmith — Mon, 20 May 2013 23:06:27 -0000

Thank you for your quick response!

Re: Using Node.js, Express, Socket.io and Exec

John Minnihan — Mon, 20 May 2013 22:33:18 -0000

In theory, you can update as many counters as you wish to place on the page. Create a separate div w/ an ID that is unique (i.e. page_one.html -> #page_one) for each.

Parse the incoming page URL (msg.pageUrl) for the pattern of interest, say 'foo.com/page_one.html' and then send any matching results to the counter div that corresponds to that page. You can do pretty much anything you need this way based upon the content of the message.

Just be sure that the url you pass back to the server is well formed wrt the pattern you are matching & you should be able to track its page load & increment its counter.

Re: Using Node.js, Express, Socket.io and Exec

Zach Goldsmith — Mon, 20 May 2013 21:49:32 -0000

What would be the best solution to live view count each page separately?

I want to keep separate live counters across several .html pages in the same node application instead of executing several nodes to do each .html page individually.

With your spin off of the healthcheck.html and code by Christophe Coenraets, I'm even more determined that this could work.

Could you point me in the right direction?

Thanks

Zach

Re: AJAX Logfile Tailer & Viewer

John Minnihan — Wed, 12 Dec 2012 08:06:30 -0000

Probably. Here's a pretty good starting point:

http://stackoverflow.com/qu...

Re: AJAX Logfile Tailer & Viewer

MAC Man — Wed, 12 Dec 2012 07:27:35 -0000

Anyway to create the start stop button as ONE Toggle ?

Re: AJAX Logfile Tailer & Viewer

Julio Olivares — Mon, 03 Dec 2012 18:43:42 -0000

Thanks! easy, clean and fast :D

Re: AJAX Logfile Tailer & Viewer

John Minnihan — Tue, 12 Jun 2012 08:08:12 -0000

Whoops! Another editing error... thanks for catching! Fixed.

Fortunately, the example has correct, functioning code.

Re: AJAX Logfile Tailer & Viewer

Matt Ackerman — Mon, 11 Jun 2012 23:48:10 -0000

After debugging this for awhile, you have a typo:

Line: 41
var currentLogValue = request1.responseText.split("\n");

should be:
var currentLogValue = request.responseText.split("\n");

Re: AJAX Logfile Tailer & Viewer

TOM — Thu, 07 Jun 2012 14:42:23 -0000

Thanks. I've had a play and have got this working using a checkbox to select if saving is needed and a text box to specify the output file name.

Using javascript I detect if the checkbox is On and then change the url to include the output file name, if it's not on then the url stays as normal.

The resulting page checks if the url has been amended and then saves the file as needed. :)
Thanks

Re: AJAX Logfile Tailer & Viewer

John Minnihan — Thu, 07 Jun 2012 09:15:30 -0000

In theory, sure.

One approach might include modifying the getLog routine to take a new parameter, the log file name, and then refactoring the URL variable to include that log file name as a query string. Then set the new log name to a javascript variable in the log tailer launch page that is passed when you click the start button.

There are undoubtedly more ways + probably some that are better.