Downloads of v


Last Update:

17 Jun 2016

Package Maintainer(s):

Software Author(s):

  • Roland Pheasant


tail log tailblazer


  • 1
  • 2
  • 3 | Updated: 17 Jun 2016



Downloads of v



Software Author(s):

  • Roland Pheasant

  • 1
  • 2
  • 3

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Passed


Scan Testing Resulted in Flagged:

This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.

We recommend clicking the "Details" link to make your own decision on installing this package.


To install TailBlazer, run the following command from the command line or from PowerShell:


To upgrade TailBlazer, run the following command from the command line or from PowerShell:


To uninstall TailBlazer, run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade tailblazer -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade tailblazer -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure tailblazer installed
    name: tailblazer
    state: present
    source: STEP 3 URL

See docs at

chocolatey_package 'tailblazer' do
  action    :install
  version  ''
  source   'STEP 3 URL'

See docs at

    Name: tailblazer,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller tailblazer
   Name     = 'tailblazer'
   Ensure   = 'Present'
   Version  = ''
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'tailblazer':
  provider => 'chocolatey',
  ensure   => '',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install tailblazer version="" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved by moderator dtgm on 20 Jun 2016.


Fast, intuitive, functionally rich tail program which is pleasing to my eyes.

$packageName = 'tailblazer'
$url = ''
$unzipLocation = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
$desktopPath = [Environment]::GetFolderPath("Desktop")
$lnkPath = $desktopPath + "\TailBlazer.lnk"
$exePath = $unzipLocation + "\" + $packageName + ".exe"

Write-Host "Uninstalling previous version"
Remove-Item $unzipLocation -Force -Recurse -Exclude $unzipLocation\logs,TailBlazer.exe.gui -ErrorAction SilentlyContinue
Write-Host "Done"

Install-ChocolateyZipPackage $packageName $url $unzipLocation
Install-ChocolateyShortcut -shortcutFilePath $lnkPath -targetPath $exePath
$desktopPath = [Environment]::GetFolderPath("Desktop")
$lnkPath = $desktopPath + "\tailblazer.lnk"

If (Test-Path $lnkPath)
	Remove-Item $lnkPath

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
TailBlazer 279 Wednesday, May 11, 2016 Approved
TailBlazer 1813 Monday, February 22, 2016 Approved
TailBlazer 0.6.340 297 Tuesday, February 23, 2016 Approved
TailBlazer 0.5.245 579 Sunday, January 10, 2016 Approved
TailBlazer 0.4.2 292 Sunday, January 10, 2016 Approved
TailBlazer 0.3 291 Sunday, January 10, 2016 Approved
TailBlazer 0.2.2 314 Sunday, January 10, 2016 Approved
TailBlazer 0.2.1 299 Sunday, January 10, 2016 Approved
TailBlazer 0.2 272 Sunday, January 10, 2016 Approved

This package has no dependencies.

Discussion for the TailBlazer Package

Ground Rules:

  • This discussion is only about TailBlazer and the TailBlazer package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or TailBlazer, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus