Downloads:

35,019

Downloads of v 368.0:

45

Last Update:

9/19/2019

Package Maintainer(s):

Software Author(s):

  • hydrusnetwork
  • anonymous

Tags:

hydrus-network admin image-database booru

Hydrus Network

This is not the latest version of Hydrus Network available.

368.0 | Updated: 9/19/2019

Downloads:

35,019

Downloads of v 368.0:

45

Maintainer(s):

Software Author(s):

  • hydrusnetwork
  • anonymous

Hydrus Network 368.0

This is not the latest version of Hydrus Network available.

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

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

>

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

>

To uninstall Hydrus Network, 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://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://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade hydrus-network -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 hydrus-network -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 hydrus-network installed
  win_chocolatey:
    name: hydrus-network
    state: present
    version: 368.0
    source: STEP 3 URL

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

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'hydrus-network' do
  action    :install
  version  '368.0'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: hydrus-network,
    Version: 368.0,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller hydrus-network
{
   Name     = 'hydrus-network'
   Ensure   = 'Present'
   Version  = '368.0'
   Source   = 'STEP 3 URL'
}

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


package { 'hydrus-network':
  provider => 'chocolatey',
  ensure   => '368.0',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install hydrus-network version="368.0" 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.

This package was approved as a trusted package on 9/19/2019.

Description

The hydrus network client is an application written for anon and other internet-fluent media nerds who have large image/swf collections. It browses with tags instead of folders, a little like a *booru on your desktop. Tags and files can be anonymously shared through custom servers that any user may run. Everything is free, and the source code is included with the release. It is developed for Windows, but fairly functional builds for Linux and OS X are released at the same time.

    The software is constantly being improved. I put out a new release every Wednesday by 8pm Eastern.

    This github repository is currently a weekly sync with my home dev environment, where I work on hydrus by myself. Feel free to fork, but please don't make pull requests at this time.

legal\LICENSE.txt
            DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
                    Version 2, December 2004

 Copyright (C) 2004 Sam Hocevar <[email protected]>

 Everyone is permitted to copy and distribute verbatim or modified
 copies of this license document, and changing it is allowed as long
 as the name is changed.

            DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

  0. You just DO WHAT THE FUCK YOU WANT TO.
legal\VERIFICATION.txt
VERIFICATION

Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

Package can be verified like this:

1. Go to

   x64: https://github.com/hydrusnetwork/hydrus/releases/download/v368/Hydrus.Network.368.-.Windows.-.Installer.exe

   to download the installer.

2. You can use one of the following methods to obtain the SHA256 checksum:
   - Use powershell function 'Get-FileHash'
   - Use Chocolatey utility 'checksum.exe'

   checksum64: E8D559081B62B02B57AE51F5D635E80A344EE4143973902283E5500113F88650

Using AU:

   Get-RemoteChecksum https://github.com/hydrusnetwork/hydrus/releases/download/v368/Hydrus.Network.368.-.Windows.-.Installer.exe


The file 'LICENSE.txt' has been obtained from <https://github.com/hydrusnetwork/hydrus/blob/master/COPYING>
tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop'
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$filePath = gi "$toolsDir\*x64.exe"

$packageArgs = @{
  packageName      = 'hydrus-network'
  fileType         = 'EXE'
  file             = "$filePath"
  softwareName     = 'Hydrus Network*'
  silentArgs       = '/VERYSILENT /SUPPRESSMSGBOXES /NORESTART /DIR="C:\Program Files\Hydrus Network"'
}

Install-ChocolateyInstallPackage @packageArgs
Remove-Item -Force -ea 0 $filePath
tools\chocolateyuninstall.ps1
$ErrorActionPreference = 'Stop';
$packageArgs = @{
  packageName   = 'hydrus-network'
  softwareName  = 'Hydrus Network*'
  fileType      = 'EXE'
  silentArgs    = "/VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-"
  validExitCodes= @(0)
}

$uninstalled = $false
[array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName']

if ($key.Count -eq 1) {
  $key | % { 
    $packageArgs['file'] = "$($_.UninstallString)"
    if ($packageArgs['fileType'] -eq 'MSI') {
      $packageArgs['silentArgs'] = "$($_.PSChildName) $($packageArgs['silentArgs'])"
      
      $packageArgs['file'] = ''
    }

    Uninstall-ChocolateyPackage @packageArgs
  }
} elseif ($key.Count -eq 0) {
  Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
  Write-Warning "$($key.Count) matches found!"
  Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
  Write-Warning "Please alert package maintainer the following keys were matched:"
  $key | % {Write-Warning "- $($_.DisplayName)"}
}
tools\Hydrus.Network.368.-.Windows.-.Installer_x64.exe
md5: EE7540A31B8B6A6DDBEDBFC1A7FAB391 | sha1: EC34E519B22ADAFD4FAFD7B48F99180B82942A15 | sha256: E8D559081B62B02B57AE51F5D635E80A344EE4143973902283E5500113F88650 | sha512: 96B47327B08EABFD002F007808E6A72BD1AD4D0996C453456ECC1A305FD2E3E40A25DFDE7FAF2C5088931533386D3BAE70BEB7B02BFFC585380AEC405F4C9D36

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
Hydrus Network 370.0 37 Friday, October 4, 2019 Approved
Hydrus Network 369.0 46 Saturday, September 28, 2019 Approved
Hydrus Network 368.0 45 Thursday, September 19, 2019 Approved
Hydrus Network 367.0 41 Thursday, September 12, 2019 Approved
Hydrus Network 366.0 29 Tuesday, September 10, 2019 Approved
Hydrus Network 365.0 65 Wednesday, August 28, 2019 Approved
Hydrus Network 363.0 60 Thursday, August 8, 2019 Approved
Hydrus Network 362.0 18 Wednesday, August 7, 2019 Approved
Hydrus Network 361.0 49 Thursday, July 25, 2019 Approved

This package has no dependencies.

Discussion for the Hydrus Network Package

Ground Rules:

  • This discussion is only about Hydrus Network and the Hydrus Network 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 Hydrus Network, 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