Downloads:

21,385

Downloads of v 0.8.0:

121

Last Update:

06 Nov 2019

Package Maintainer(s):

Software Author(s):

  • Fndroid

Tags:

clash v2ray shadowsocks

Clash for Windows

This is not the latest version of Clash for Windows available.

  • 1
  • 2
  • 3

0.8.0 | Updated: 06 Nov 2019

Downloads:

21,385

Downloads of v 0.8.0:

121

Maintainer(s):

Software Author(s):

  • Fndroid

  • 1
  • 2
  • 3
Clash for Windows 0.8.0

This is not the latest version of Clash for Windows available.

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Clash for Windows, run the following command from the command line or from PowerShell:

>

To upgrade Clash for Windows, run the following command from the command line or from PowerShell:

>

To uninstall Clash for Windows, run the following command from the command line or from PowerShell:

>

Deployment Method:

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

1. Enter Your Internal Repository Url

(this should look similar to https://community.chocolatey.org/api/v2/)


2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • 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. Copy Your Script

choco upgrade clash-for-windows -y --source="'INTERNAL REPO URL'" --version="'0.8.0'" [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 clash-for-windows -y --source="'INTERNAL REPO URL'" --version="'0.8.0'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Install clash-for-windows
  win_chocolatey:
    name: clash-for-windows
    version: '0.8.0'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'clash-for-windows' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '0.8.0'
end

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


cChocoPackageInstaller clash-for-windows
{
    Name     = "clash-for-windows"
    Version  = "0.8.0"
    Source   = "INTERNAL REPO URL"
}

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


package { 'clash-for-windows':
  ensure   => '0.8.0',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

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


4. 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 Pauby on 28 Nov 2019.

Description

Clash

A rule-based tunnel in Go.

Clash for Windows

A Windows GUI based on Clash


tools\chocolateyinstall.ps1

$ErrorActionPreference = 'Stop';
#$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url = 'https://github.com/Fndroid/clash_for_windows_pkg/releases/download/0.8.0/Clash.for.Windows.Setup.0.8.0.exe'
$checksum = '01dfc9cb8e23bc90e0453c70651b91b2cb8c15611ccf4bdc5dae07255c8235b0'

$packageArgs = @{
  packageName    = $env:ChocolateyPackageName
  fileType       = 'exe'
  url            = $url

  softwareName   = 'Clash for Windows*'

  checksum       = $checksum
  checksumType   = 'sha256'

  validExitCodes = @(0, 3010, 1641)
  silentArgs     = '/S'
}

Install-ChocolateyPackage @packageArgs
tools\chocolateyuninstall.ps1
$ErrorActionPreference = 'Stop';
$packageArgs = @{
  packageName    = $env:ChocolateyPackageName
  softwareName   = 'Clash for Windows*'
  fileType       = 'exe'
  validExitCodes = @(0, 3010, 1605, 1614, 1641)
  silentArgs     = '/S'
}

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

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

    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)" }
}

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.

Add to Builder Version Downloads Last Updated Status
Clash for Windows 0.19.18 77 Monday, May 16, 2022 Approved
Clash for Windows 0.19.17 232 Saturday, April 30, 2022 Approved
Clash for Windows 0.19.15 360 Saturday, April 9, 2022 Approved
Clash for Windows 0.19.14 156 Friday, April 1, 2022 Approved
Clash for Windows 0.19.13 118 Monday, March 28, 2022 Approved
Clash for Windows 0.19.10 465 Friday, February 25, 2022 Approved
Clash for Windows 0.19.9 42 Friday, February 25, 2022 Approved
Clash for Windows 0.19.8 122 Thursday, February 17, 2022 Approved
Clash for Windows 0.19.7 315 Friday, January 28, 2022 Approved

This package has no dependencies.

Discussion for the Clash for Windows Package

Ground Rules:

  • This discussion is only about Clash for Windows and the Clash for Windows 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 Clash for Windows, 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