Downloads:
3,227
Downloads of v 1.3.0:
1,616
Last Update:
08 Feb 2018
Package Maintainer(s):
Software Author(s):
- Badgerati
Tags:
fudge powershell automation provision devops json windows software deployment packages package-manager pack install manager- Software Specific:
- Software Site
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Fudge
- 1
- 2
- 3
1.3.0 | Updated: 08 Feb 2018
- Software Specific:
- Software Site
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
3,227
Downloads of v 1.3.0:
1,616
Maintainer(s):
Software Author(s):
- Badgerati
Fudge 1.3.0
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Badgerati. The inclusion of Badgerati trademark(s), if any, upon this webpage is solely to identify Badgerati goods or services and not for commercial purposes.
- 1
- 2
- 3
All Checks are Passing
3 Passing Tests
Deployment Method: Individual Install, Upgrade, & Uninstall
To install Fudge, run the following command from the command line or from PowerShell:
To upgrade Fudge, run the following command from the command line or from PowerShell:
To uninstall Fudge, run the following command from the command line or from PowerShell:
Deployment Method:
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
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
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
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download fudge --internalize --source=https://community.chocolatey.org/api/v2/
-
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'"
- Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade fudge -y --source="'INTERNAL REPO 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 fudge -y --source="'INTERNAL REPO URL'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install fudge
win_chocolatey:
name: fudge
version: '1.3.0'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'fudge' do
action :install
source 'INTERNAL REPO URL'
version '1.3.0'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller fudge
{
Name = "fudge"
Version = "1.3.0"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'fudge':
ensure => '1.3.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 as a trusted package on 12 Nov 2024.
Fudge is a PowerShell tool to help manage software packages via Chocolatey for specific development projects. Think NPM and Bower, but for Chocolatey.
Features
- Uses a Fudgefile to control required software
- Allows you to version control required software to run websites, services and applications
- Ability to run pre/post install/upgrade/downgrade/uninstall/pack scripts
- Can seperate out developer specific software which aren't needed for certain environments
- You can reinstall all packages, or just in/un/reinstall all packages
- Allows you to have mutliple nuspecs, which you can then pack one or all of with Fudge
- See details about packages in a Fudgefile - such as which ones are installed or need upgrading
- Create empty template Fudgefiles, or create them from nuspec files
- Prune the machine to remove packages not in a Fudgefile (except chocolatey/fudge obviously!)
- Clean a machine of all packages installed (again, except chocolatey/fudge)
# Uninstall
function Remove-Fudge($path)
{
$current = (Get-EnvironmentVariable -Name 'PATH' -Scope 'Machine')
$current = $current.Replace($path, [string]::Empty)
Set-EnvironmentVariable -Name 'PATH' -Value $current -Scope 'Machine'
Update-SessionEnvironment
}
$path = Join-Path $env:chocolateyPackageFolder 'tools/src'
$pathSemi = "$($path);"
Write-Host 'Removing Fudge from environment Path'
if (($env:Path.Contains($pathSemi)))
{
Remove-Fudge $pathSemi
}
elseif (($env:Path.Contains($path)))
{
Remove-Fudge $path
}
Log in or click on link to see number of positives.
- fudge.1.3.0.nupkg (47463e41164c) - ## / 60
- 1.3.0-Binaries.zip (0dc579f290f9) - ## / 60
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 |
---|---|---|---|---|
Fudge 1.3.0 | 1616 | Thursday, February 8, 2018 | Approved | |
Fudge 1.2.1 | 397 | Thursday, January 18, 2018 | Approved | |
Fudge 1.2.0 | 402 | Monday, September 4, 2017 | Approved | |
Fudge 1.1.0 | 388 | Thursday, August 24, 2017 | Approved | |
Fudge 1.0.0 | 424 | Sunday, August 6, 2017 | Approved |
Copyright 2017
This package has no dependencies.
Ground Rules:
- This discussion is only about Fudge and the Fudge 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 Fudge, 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.