Slimed down C5
Permalink
30.8 MB of data isn't a whole lot. However, the danger of C5 is that when you build a site, other folks like it so much they want you to build another, and another, and ... well you get the point. I am now building my 5th C5 site in under two months on my hosting plan. That said, I'm getting to about 50% of my storage in that plan.
So the question is, how do you slim down your installs of C5 to as little as possible while still working correctly.
Most language files seem to me to be unnecessary most of the time. However, I still don't know where they are located (nborders-is a touch lazy).
Some theme images, etc.
What say you?
~n
So the question is, how do you slim down your installs of C5 to as little as possible while still working correctly.
Most language files seem to me to be unnecessary most of the time. However, I still don't know where they are located (nborders-is a touch lazy).
Some theme images, etc.
What say you?
~n
well all the js, and CSS needs to be minified,
you can remove themes, blocks, unused languages, compress images etc
you can remove themes, blocks, unused languages, compress images etc
there is always the option to use 1 core :)
I can't imagine removing whitespace from javascript files is going to have much of an impact on the total package size.
I think you can certainly delete old cores as you upgrade now. Mnkras's suggestion of setting up a shared core box as our hosting partner program outlines is a good one if you're really going to be dealing with dozens of installs.
best
I think you can certainly delete old cores as you upgrade now. Mnkras's suggestion of setting up a shared core box as our hosting partner program outlines is a good one if you're really going to be dealing with dozens of installs.
best
http://www.concrete5.org/community/forums/customizing_c5/autonav-re...
I'd like to know what the recommended protocol is for dealing with accumulating updates. Deleting them manually would seem to cause no harm as long as you're sure the ones to be deleted aren't being used (if you're sharing a core across multiple sites).
-Steve