From: mose <mo...@fe...> - 2003-09-07 04:43:50
|
le Sat, Sep 06, 2003 at 09:09:29PM -0700 par Michael Wexler : > Hi, gang! > > I pulled down 1.7.1.1 to see how things have changed, and among the > many improvements is the complete ballooning in size. Even after my > usual tricks of deleting the avatar images and the extra languages, > Tiki is a monster collection of files. I have only 20 megs of space on > my ISP (I'm cheap!), and after expanding Tiki, I had no room for > anything else! > > Do we (or, should we) have a page on Tiki called, say, SmallTiki, which > tells how to gracefully remove features and directories (like the 2.3 > megs of pdflib, or the 1.2 megs of Galaxia docs) that the user may not > need for a basic Tiki? - I made such a package, but never finished it. Check in file docs/devel/tikirelease.sh there is a bunch of commented lines that were intended to build a tikilight version with minimal disk occupation. Result is about 17Mo expanded, 2.3Mo bzipped. I guess some more stuff can be omittted to gain more space. if you don't plan to use pdf generation you can gain 1Mo with lib/pdflib content. Galaxia removal can save another 1Mo. If you already have a pear, there is also lib/pear maybe that can be dropped (expected pear is in your path) for another 800K. With some jHotDraw, jpgraph and jgraphpad removal, 1.5Mo can be saved again. It should be possible to be around 10Mo maybe with some efforts. > Also, how resilient is Tiki to removal of certain features? If a user > just ignores jgraphpad (600k) or some of the tiki- files, what might > happen? Should I leave just one avatar, or will something crash? If a > user decides to upload libraries later, will things automagically start > working? - you can remove libs and put them later. Just avoid to activate features that involve such things. But I guess it has to be tested. Tiki is big and his internal stuff > It's funny: I like Tiki b/c everything is integrated. But now, with so > much in Tiki that I won't use, the integration is somewhat of a pain. > But only a bit! > > Finally, I don't know if anyone has done this yet, but it might be > useful to include a "Clear out Templates_c" button somewhere. I had to > hunt through the archives to figure out how to delete these on my > server; they were owned by nobody! I finally wrote a php page which, > when called, clears them out, and the function (taken straight from the > php docs) could easily be added to an admin/utility page somewhere, I > bet. And if its already there, sorry to waste everyones time: I have > to continue carving away before I can get it installed. - true. that's on some todo lists. we need such page in admin range. > But on first glance, things look great; you guys are amazing. - the sum of us is. individually, we all suck. regards, mose |