Buster: Hits a set of urls periodically to bust caches

[ mit, program, web ] [ Propose Tags ]

Buster is a simple tool to periodically make requests to a list of URLs. The main use case for this is to bust caches.

[Skip to Readme]
Versions [RSS] [faq] 0.1.0, 0.1.1
Dependencies base (==4.*), bytestring, conduit (==0.5.*), data-default (==0.5.*), errors (==1.4.*), hinotify (==0.3.*), hslogger (==1.2.*), http-conduit (==1.8.*), http-types (==0.7.*), transformers, unbounded-delays (==0.1.*), unix (>=, yaml (==0.8.*) [details]
License MIT
Copyright (c) 2012 Michael Xavier
Author Michael Xavier <michael@michaelxavier.net>
Maintainer Michael Xavier <michael@michaelxavier.net>
Category Web
Home page http://github.com/michaelxavier/Buster
Bug tracker http://github.com/michaelxavier/Buster/issues
Source repo head: git clone git://github.com/MichaelXavier/Buster.git
Uploaded by MichaelXavier at 2013-05-22T06:11:22Z
Distributions NixOS:0.1.1
Executables buster
Downloads 1960 total (10 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Hackage Matrix CI
Docs not available [build log]
All reported builds failed as of 2016-10-24 [all 15 reports]


Maintainer's Corner

For package maintainers and hackage trustees


Readme for Buster-0.1.1

[back to package description]


Build Status

Hey Brother!

Utility for periodically hitting URLs. The intended use case is forcing caches to be busted.


Run make. Use a recent version of GHC. Requires cabal-dev.


buster config.yml

The program will log to stdout. If you want to reload the config without stopping the program, send it a HUP signal:

kill -HUP pid-of-buster


Take a look in the example directory. Buster is configured with a yaml file:

verbose: true
monitor: false
log_file: /var/log/buster.log
- url: http://www.example.com
  interval: 5
  method: GET
- url: http://www.example.net
  interval: 2
  method: GET

Interval is measured in seconds. Monitor will begin auto-loading your config. If you have a process running and you decide you want the config monitored, send a HUP to the process and from then on it will monitor the file. If no log_file config is specified, it will log to stdout.


The project currently works. Here are some improvements I want to make

  • Release to hackage


  1. Fork the project.
  2. Make your changes in a feature branch.
  3. Run tests with make test.
  4. Send a pull request.