index.html in thinner-0.1.0 vs index.html in thinner-0.1.1
- old
+ new
@@ -1,30 +1,31 @@
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html;charset=UTF-8" />
- <title>Thinner -- Version 0.1.0
+ <title>Thinner -- Version 0.1.1
</title>
<link rel="stylesheet" type="text/css" href="documentation/css/styles.css" />
<link rel="stylesheet" type="text/css" href="documentation/css/dawn.css" />
</head>
<body>
<a href="http://www.propublica.org" class="propublica"> </a>
- <h1>Thinner – Version 0.1.0
+ <h1>Thinner – Version 0.1.1
</h1>
- <p><a href="https://github.com/propublica/Thinner">Thinner</a> is a utility
+ <p><a href="https://github.com/propublica/thinner">Thinner</a> is a utility
for purging urls from a Varnish server.</p>
<p>When you are deploying code changes to a server under load, the uncached
load can quickly bring down your backend server even with Varnish's grace
mode. Often, allowing stale caches to stick around for a while saves
both server performance and sanity.</p>
<p>Thinner gives you fine-grained control over wildcard purging, and rolls
purges out slowly. Your users will see stale pages from the previous deploy
until Thinner has finished invalidating the stale cache at a rate that you set.
- If you have a bunch of pages you need to invalidate en masse, but don't
- want to risk overloading your server, Thinner is for you.</p>
+ If you have a bunch of pages you need to invalidate en masse and at infrequent
+ intervals (e.g. deploys, timed remote api updates), but don't want to
+ risk overloading your server, Thinner is for you.</p>
<p>All that being said, Thinner isn't really a solution for observing
model changes and purging associated urls. If you have a highly dynamic
application, it's worlds better to handle purging via a
<a href="http://github.com/russ/lacquer/blob/master/lib/lacquer/delayed_job_job.rb">job server</a>
outside of the request-response flow.</p>
@@ -64,11 +65,11 @@
</pre>
<p>Once you have the configuration in place call <strong>purge!</strong> with
an array of urls:</p>
<pre class="dawn"><span class="Comment"><span class="Comment">#</span> The urls in this array are purged in order, so you'll want to structure it</span>
<span class="Comment"><span class="Comment">#</span> according to usage.</span>
-arr <span class="Keyword"><<</span> ["/some_route"<span class="PunctuationSeparator">,</span> "/"]
+arr <span class="Keyword"><<</span> ["/some_route"<span class="PunctuationSeparator">,</span> "/some_route/with.*"<span class="PunctuationSeparator">,</span> "/"]
<span class="Support">Thinner</span><span class="PunctuationSeparator">.</span><span class="Entity">purge!</span> arr
</pre>
<p>Thinner will then fork a background process and purge the urls. You can
check the progress of the purge by tailing the log file or with:</p>
@@ -79,9 +80,11 @@
<p>The command line interface accepts a newline separated list of urls via
stdin by setting the <strong>-e</strong> flag. So you'll be able to use
the command like so:</p>
<pre>cat urls_to_purge.txt | bin/thinner -e</pre>
<h2>Change Log</h2>
+ <h3>0.1.1</h3>
+ <p>Fixed bug in command line argument parsing.</p>
<h3>0.1.0</h3>
<p>Initial release.</p>
</body>
</html>
\ No newline at end of file