Forge Home


Puppet module to manage tinyproxy


16,433 latest version

4.3 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 1.1.0 (latest)
  • 1.0.3
  • 1.0.2
  • 1.0.1 (deleted)
  • 1.0.0 (deleted)
released Feb 21st 2018
This version is compatible with:
  • Puppet Enterprise >=3.0.0
  • Puppet >=2.7.20 <5.0.0
  • , , ,

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'earsdown-tinyproxy', '1.1.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add earsdown-tinyproxy
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install earsdown-tinyproxy --version 1.1.0

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.



earsdown/tinyproxy — version 1.1.0 Feb 21st 2018

What is it?

A Puppet module that manages tinyproxy

A fork of Johan Lyheden's excellent tinyproxy puppet module with the following enhancements:

  • Manage the contents of the filter file (via new filtercontent parameter)
  • Debug support switches DefaultErrorFile to use debug.html (enable via new debugmode parameter)
  • Manage the XTinyproxy configuration directive (via new xtinyproxy parameter)
  • Alignment with the Puppet style guide and address puppet-lint warnings

Released under the Apache 2.0 license



You can install, configure and start the service simply by including the class

include tinyproxy

The module supports most of tinyproxy's parameters, check init.pp for more details. Here's an example on how to override a few parameters:

class { 'tinyproxy':
  listen             => '',
  port               => '8080',
  connection_timeout => '60',

In addition you can add ACLs, headers and upstream proxies via separate resource definitions:

tinyproxy::header { 'X-My-Header':
  value  => 'Powered by Tinyproxy'

tinyproxy::upstream { 'my_upstream':
  proxy  => 'myproxy:8080',
  match  => ''

tinyproxy::noupstream { 'my_noupstream':
  match  => ''

tinyproxy::reversepath { 'my_reversepath':
  path   => '/mypath/',
  target => ''


  • Fork it
  • Create a feature branch
  • Make your changes
  • Submit a PR