GeoServer docs clocked in at 15 megs last release. This is ridiculous. Initial look seems to indicate that at least half of it is due to one shapefile download. And another bunch is in big, duplicated pdf files. These can be moved to GEOS, where they won't be sucked into the download.
Environment
None
Activity
codehaus
April 10, 2015 at 4:36 PM
CodeHaus Comment From: aaime - Time: Thu, 29 Mar 2007 02:06:35 -0500 ---------------------
<p>These issue has been in resolved state for at least one month (quite a bit, a lot more than one month). Batch transitioning them to closed state</p>
codehaus
April 10, 2015 at 4:36 PM
CodeHaus Comment From: cholmes - Time: Tue, 10 Jan 2006 17:30:18 -0600 ---------------------
<p>Ok, there's actually a bit more clean-up I'd like to do at some point, but I think what I did should take it down to 5 megs or less, which is acceptable, though not quite ideal. There is a 300kb sql file that I'd like to move out, but first I'd like to see the interaction with attachments on the html exported files. Like do we need to put links on the pages? If so we should clean up a few of the pages to list all the links of their attachments, and doing so will make it easier to move off.</p>
<p>There are also maybe 6 screenshots that clock in at 300kb+. One is a nice UML diagram, that probably needs to stay that large, but the others can probably be shrunk to smaller sizes...</p>
GeoServer docs clocked in at 15 megs last release. This is ridiculous. Initial look seems to indicate that at least half of it is due to one shapefile download. And another bunch is in big, duplicated pdf files. These can be moved to GEOS, where they won't be sucked into the download.