X-Git-Url: https://git.sesse.net/?a=blobdiff_plain;f=files%2Ffaq.html;h=54007cde6a9a7b75e7f86cd8d13e6143b7676259;hb=7f954ef5ec86c9ab790a89a9c153190bedfea54c;hp=90eb5ee8cb42a8939fb4dc9dd541e59ca79a8fa9;hpb=b5d44d73bfa40fe7dc234a95dc3f8f81ec88398f;p=pr0n diff --git a/files/faq.html b/files/faq.html index 90eb5ee..54007cd 100644 --- a/files/faq.html +++ b/files/faq.html @@ -9,7 +9,7 @@
Last updated March 23rd, 2009
+Last updated November 20th, 2015
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 Apache 2.2, - mod_perl 2.0, - ImageMagick 6.x +
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 PSGI + app server running under Starlet + behind Varnish 4.1, + using ImageMagick 6.x (as well as various other Perl modules) and - qscale, using - PostgreSQL 8.3 as the back-end + qscale, using + PostgreSQL 9.4 as the back-end database for metadata et al. The base operating system is - Debian lenny (ie. âtestingâ).
+ Debian jessie.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.
At the time of writing, approximately 160GB of image data (that is, over - 69000 different images), plus cache, plus metadata in the SQL database. +
At the time of writing, approximately 1014GB of image data (that is, over + 258000 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.)
@@ -114,10 +114,10 @@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 - http://bzr.sesse.net/pr0n/, but + favourite Linux distribution. There is a git repository at + http://git.sesse.net/pr0n/, 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.)
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 ;-)
-Try e-mail, or reach me on IRC as Sesse on EFnet, IRCnet, Freenode or OFTC.