Downloads:

8,674

Downloads of v 1.1.22:

5,475

Last Update:

10 Aug 2018

Package Maintainer(s):

Software Author(s):

  • DocFetcher Development Team

Tags:

docfetcher admin

DocFetcher (Install)

  • 1
  • 2
  • 3

1.1.22 | Updated: 10 Aug 2018

Downloads:

8,674

Downloads of v 1.1.22:

5,475

Maintainer(s):

Software Author(s):

  • DocFetcher Development Team

  • 1
  • 2
  • 3
DocFetcher (Install) 1.1.22

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Failed

Details

Scan Testing Successful:

No detections found in any package files

Details

To install DocFetcher (Install), run the following command from the command line or from PowerShell:

>

To upgrade DocFetcher (Install), run the following command from the command line or from PowerShell:

>

To uninstall DocFetcher (Install), 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 https://community.chocolatey.org/api/v2. 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 https://community.chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade docfetcher -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 docfetcher -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Ensure docfetcher installed
  win_chocolatey:
    name: docfetcher
    state: present
    version: 1.1.22
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'docfetcher' do
  action    :install
  version  '1.1.22'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: docfetcher,
    Version: 1.1.22,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller docfetcher
{
   Name     = 'docfetcher'
   Ensure   = 'Present'
   Version  = '1.1.22'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'docfetcher':
  provider => 'chocolatey',
  ensure   => '1.1.22',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


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

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

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 as a trusted package on 29 Jan 2020.

Description

DocFetcher is an Open Source desktop search application: It allows you to search the contents of files on your computer. — You can think of it as Google for your local files. The application runs on Windows, Linux and Mac OS X, and is made available under the Eclipse Public License.


tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop';
$packageName = 'DocFetcher' 
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$registryUninstallerKeyName = 'DocFetcher' 
$installerType = 'EXE' 
$url = 'http://sourceforge.net/projects/docfetcher/files/docfetcher/1.1.22/docfetcher_1.1.22_win32_setup.exe/download' 
$silentArgs = '/S' 
$validExitCodes = @(0) 
$checksum      = 'cd2c647ca05cb5000b1d9b07d6dfa04e6c3d6441ba09bdf05bc2acecbf78d9d4'
$checksumType  = 'sha256'

$packageArgs = @{
  packageName   = $packageName
  unzipLocation = $toolsDir
  fileType      = $installerType
  url           = $url
  silentArgs    = $silentArgs 
  validExitCodes= @(0)
  checksum      = $checksum
  checksumType  = $checksumType
  softwareName  = $packageName
}



Stop-Process -Name docfetcher-daemon-windows.exe -Confirm -Debug -ErrorAction SilentlyContinue
Stop-Process -Name DocFetcher.exe -Confirm -Debug -ErrorAction SilentlyContinue
Install-ChocolateyPackage @packageArgs

tools\chocolateyuninstall.ps1
# stop on all errors
$ErrorActionPreference = 'Stop';
$packageName = 'DocFetcher'
$registryUninstallerKeyName = 'DocFetcher' #ensure this is the value in the registry
$installerType = 'EXE'
$silentArgs = '/S'
$validExitCodes = @(0)

$osBitness = Get-ProcessorBits
 
if ($osBitness -eq 64) {
  $file = (Get-ItemProperty -Path "hklm:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\$registryUninstallerKeyName").UninstallString
} else {
  $file = (Get-ItemProperty -Path "hklm:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\$registryUninstallerKeyName").UninstallString
} 
	
Uninstall-ChocolateyPackage -PackageName $packageName -FileType $installerType -SilentArgs $silentArgs -validExitCodes $validExitCodes -File $file

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
DocFetcher (Install) 1.1.19 1537 Wednesday, January 11, 2017 Approved
DocFetcher (Install) 1.1.18 420 Tuesday, July 26, 2016 Approved
DocFetcher 1.1.17 307 Monday, March 14, 2016 Approved
DocFetcher (Install) 1.1.16 309 Monday, September 7, 2015 Approved
DocFetcher (Install) 1.1.15 316 Saturday, August 29, 2015 Approved
DocFetcher (Install) 1.1.14 310 Saturday, May 30, 2015 Approved

Discussion for the DocFetcher (Install) Package

Ground Rules:

  • This discussion is only about DocFetcher (Install) and the DocFetcher (Install) 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 DocFetcher (Install), 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