Thanks for your insight which verbosely matches the spartan 300. :) used in an article, and MediaWiki will dutifully generate a thumbnail of that size. Yeah, this makes sense and is good to know. of thumbnails of arbitrary sizes, and limit it to some preset list. Good to know, too. So the SSD-harddrive-with-not-enough-space-battle may continue. :) I will also try to find a nice place on the wiki to docu the info. Thanks and cheers Karsten Am 27.02.2017 um 17:54 schrieb Bartosz Dziewoński:

I think only the default value of wgImageLimits would actually do anything for this. The other limits Are only triggered for people with non default preferences. If you dont care about things looking nice on high dpi displays (e.g. apple retina type things) you could set $wgResponsiveImages You could disable thumbnailing outright and transfer the full sized image to the browser - $wgUseImageResize Beyond that you could do something really complicated, like set up 404 thumb handling and then have a cron script use the find command to delete any thumbnails that havent been accessed recently or are non standard size. Hope that helps. MW thumbnailing really is not optimized for the usecase of low hard disk space. -- bawolff On Wednesday, March 1, 2017, [[kgh]] <mediawiki(a)kghoffmeyer.de> wrote: "$wgImageLimits" AND to the "$wgThumbLimits" configuration setting. If one for example sets the following for a minimum initial creation of thumbs: file pages), 180 (default preview size on "Special:ListFiles") as well as 320 (default size for thumbs), 480 (1.5x of default size for thumbs) and 640 (2x of default size for thumbs) would be created. To be frank, thumb generation is indeed not controllable at all. page itself. For example, for this random file: https://commons.wikimedia.org/wiki/File:Bruxelles_à_travers_les_âges_(1884)… "File history" is 120×90. generated to be used on devices with high-resolution screens. in an article, and MediaWiki will dutifully generate a thumbnail of that size. thumbnails of arbitrary sizes, and limit it to some preset list.

You could make the wiki read only using $wgReadOnly. You can even add a nice message indicating that the project has completed, therefore the wiki is now read only. On Thu, Mar 2, 2017 at 9:41 AM, Valeri Galtsev <galtsev(a)kicp.uchicago.edu> wrote:

The HTML format dumps (not yet ready but soon, I promise!) may not be sufficient for stand-alone use, but a simple wrapper unrelated to MediaWiki ought to be able to serve them up with basic navigation; you'd still have to deal with searches somehow but that's true for any static HTML dump. Or am I misunderstanding folks' needs here? Ariel On Fri, Mar 10, 2017 at 10:24 AM, Federico Leva (Nemo) <nemowiki(a)gmail.com> wrote:

Heiya Valeri, please use as new thread for new questions. Apart from that you may probably want to look into HTTrack [0]. Cheers Karsten [0] *http://www.httrack.com/* Am 02.03.2017 um 15:41 schrieb Valeri Galtsev: