</head>
<body>
<h1>pr0n FAQ</h1>
- <p>Last updated March 23rd, 2009</p>
+ <p>Last updated November 20th, 2015</p>
<h2>So, what is this pr0n thing anyway?</h2>
Also, it has dynamical rescaling (of good quality — proper,
sharp thumbnails, no crappy nearest-neighbor scaling) of both thumbnails
and images (most client-side scaling sucks quality-wise, unfortunately),
- an easy-to-use <a href="http://www.webdav.org/">WebDAV</a>-based upload
+ an easy-to-use HTML5 upload
interface, cache awareness and in general good performance (being a set
of persistent, optimized Perl modules; I've seen it throw out over 300
- hits a second even without the Squid in front, but I won't guarantee it
+ hits a second even without the Varnish in front, but I won't guarantee it
would withstand a Slashdot attack ;-) ). Also, it has quite OK skinning
capabilities, so it's able to adapt into different designs quite
easily.</p>
<h2>What hardware/software does it run on?</h2>
- <p>pr0n currently runs on an Intel Q9450 (quad-core 2.66GHz) with 8GB RAM and ordinary
- SATA disks. (The server does a lot of other stuff besides running pr0n, of
- course.) pr0n itself is a custom-made system by myself, tightly coupled
- into <a href="http://www.apache.org/">Apache</a> 2.2,
- <a href="http://perl.apache.org/">mod_perl</a> 2.0,
- <a href="http://www.imagemagick.org/">ImageMagick</a> 6.x
+ <p>pr0n currently runs on two Intel E5-2650v3 (2x10 cores at 2.30GHz) with 64GB RAM and
+ SATA disks, with some SSDs in front for cache. (The server does a lot of other stuff besides running pr0n, of
+ course.) pr0n itself is a custom-made system by myself,
+ a <a href="http://search.cpan.org/~miyagawa/PSGI-1.102/PSGI.pod">PSGI</a>
+ app server running under <a href="http://search.cpan.org/dist/Starlet/">Starlet</a>
+ behind <a href="https://www.varnish-cache.org/">Varnish</a> 4.1,
+ using <a href="http://www.imagemagick.org/">ImageMagick</a> 6.x
(as well as various other Perl modules) and
- <a href="http://bzr.sesse.net/qscale/">qscale</a>, using
- <a href="http://www.postgresql.org/">PostgreSQL</a> 8.4 as the back-end
+ <a href="http://git.sesse.net/?p=qscale">qscale</a>, using
+ <a href="http://www.postgresql.org/">PostgreSQL</a> 9.4 as the back-end
database for metadata et al. The base operating system is
- <a href="http://www.debian.org/">Debian</a> lenny (ie. “testing”).</p>
+ <a href="http://www.debian.org/">Debian</a> jessie.</p>
<p>The Perl modules aren't really that big — we're talking about only
- approx. 3300 lines of code (of which ~25% is the WebDAV part; I should
- really make that a bit cleaner once). Most of the real work is done by
+ approx. 2600 lines of code. Most of the real work is done by
the software on which pr0n builds on.</p>
<h2>How much data is there in there, anyway?</h2>
- <p>At the time of writing, approximately 250GB of image data (that is, over
- 88000 different images), plus cache, plus metadata in the SQL database.
+ <p>At the time of writing, approximately 720GB of image data (that is, over
+ 195000 different images), plus cache, plus metadata in the SQL database.
(These numbers are growing rather rapidly, so they could be outdated at
any given time.)</p>
<p>Probably, but are you sure you can get it to work? It's
non-trivial to set up, as it depends on lots of odd modules and a lot of
custom configuring; this is not a pre-made, user friendly package for your
- favourite Linux distribution. There is a bzr repository at
- <a href="http://bzr.sesse.net/pr0n/">http://bzr.sesse.net/pr0n/</a>, but
+ favourite Linux distribution. There is a git repository at
+ <a href="http://git.sesse.net/?p=pr0n">http://git.sesse.net/pr0n/</a>, but
I'm not going to hold your hand configuring it. :-) (Hint: If you do not
- know what bzr is, and cannot find out on your own, pr0n is not for
+ know what git is, and cannot find out on your own, pr0n is not for
you.)</p>
<h2>Will you implement feature X?</h2>
the images :-) If you really have a novel or cool feature, feel
free to contact me (see below).</p>
- <h2>Is the upload WebDAV server RFC-compliant?</h2>
-
- <p>Unfortunately, no. When and if somebody makes a sane framework for
- making WebDAV servers I can use, it probably will, but ATM it's just
- too much work for what I need it for. It would be a lot easier if
- I only had to support WebDAV level 1, but due to silly restrictions
- in Mac OS X' WebDAV client I have to support WebDAV level 2 as well,
- and, well, most of that is faked. ;-) In addition, there are multiple
- minor features in the system (like autorenaming files on name clashes)
- that just aren't easy to adapt to WebDAV. The WebDAV service is
- restricted, though, so I guess rather few people will get hurt just
- because I'm not fully compliant ;-)</p>
-
<h2>How do I get in touch with you?</h2>
<p>Try <a href="mailto:sgunderson@bigfoot.com">e-mail</a>, or reach me
on IRC as Sesse on EFnet, IRCnet, Freenode or OFTC.</p>
<hr />
- <p class="footer">pr0n v2.70,
- © 2004-2008 <a href="http://www.sesse.net/">Steinar H. Gunderson</a>.</p>
+ <p class="footer">pr0n v3.10,
+ © 2004–2015 <a href="https://www.sesse.net/">Steinar H. Gunderson</a>.</p>
</body>
</html>
projects / pr0n / blobdiff