Minimal Installation
Permalink
I have Concrete5 installed for test and development purposes for some time now, and never had to worry much about the amount of space disk it takes until now, since that's not usually such a big deal.
But I was faced recently with such an issue, as I need to get Concrete5 up and running taking less storage space than usual. I need my whole installation (C5, with a lightweight theme and no add-ons, and some content and media for the site) to fit in under 50MB. The ideal situation was for C5 to take close to 45MB to free around 5MB for the rest I need to store along with it.
I only need the C5 to act as a CMS for a small site, managing a handful of pages with no growing and no other functionality requirements of any kind.
Bottom line, is there any reliable definition of a minimal and functional C5 installation that I can use for that purpose?
But I was faced recently with such an issue, as I need to get Concrete5 up and running taking less storage space than usual. I need my whole installation (C5, with a lightweight theme and no add-ons, and some content and media for the site) to fit in under 50MB. The ideal situation was for C5 to take close to 45MB to free around 5MB for the rest I need to store along with it.
I only need the C5 to act as a CMS for a small site, managing a handful of pages with no growing and no other functionality requirements of any kind.
Bottom line, is there any reliable definition of a minimal and functional C5 installation that I can use for that purpose?
Within your remit, that is probably OK.
With the TinyMCE files deleted you may get some 404 errors on loading resources. You may need to override or hack the content block controller to not load any assets. Or simply replace all content block code with html block code.
TinyMCE is also used by rich text attributes, so you may have to apply similar hacks to text attributes.
Same note about 404 errors on the deleted icons. It may be safer to replace them with icons that compress better, such as single color splodges of the same size.
Remember to disable page statistics and error logging.
Perhaps install my Extreme Clean job and cron it to run every night.
Many of the shipped c5 javascript and css files are pre built into ccm.app.js/ccm.app.css and are not actually used directly, so could be deleted to save a few kb.
There may also be unused stuff in the 3rdparty libraries shipped with the core.
The core ships with themes you may not want and could be uninstalled and stripped out.
You could also disable the dashboard core upgrade, newsflow, marketplace integration etc. There is a howto on white labelling with details about that.
I seem to remember a howto that had more detailed notes about lightweight installations, but cant find it.
With the TinyMCE files deleted you may get some 404 errors on loading resources. You may need to override or hack the content block controller to not load any assets. Or simply replace all content block code with html block code.
TinyMCE is also used by rich text attributes, so you may have to apply similar hacks to text attributes.
Same note about 404 errors on the deleted icons. It may be safer to replace them with icons that compress better, such as single color splodges of the same size.
Remember to disable page statistics and error logging.
Perhaps install my Extreme Clean job and cron it to run every night.
Many of the shipped c5 javascript and css files are pre built into ccm.app.js/ccm.app.css and are not actually used directly, so could be deleted to save a few kb.
There may also be unused stuff in the 3rdparty libraries shipped with the core.
The core ships with themes you may not want and could be uninstalled and stripped out.
You could also disable the dashboard core upgrade, newsflow, marketplace integration etc. There is a howto on white labelling with details about that.
I seem to remember a howto that had more detailed notes about lightweight installations, but cant find it.
Thanks for the ideas, John. I'll keep alert for the problems you point out.
So far, the only consequence I've seen for taking tinyMCE out was the swap from the usual editor to a plain text HTML editor where it was.
As for the icons, I think it won't make a big difference, as the final installation will only show a site with a few pages, and I don't foresee the need for them, but I'll keep your solution for it in mind.
For the moment, I think I was able to "improvise" a functional lightweight installation! :)
So far, the only consequence I've seen for taking tinyMCE out was the swap from the usual editor to a plain text HTML editor where it was.
As for the icons, I think it won't make a big difference, as the final installation will only show a site with a few pages, and I don't foresee the need for them, but I'll keep your solution for it in mind.
For the moment, I think I was able to "improvise" a functional lightweight installation! :)
/languages : emptied this folder completely, keeping the empty folder (8.5MB);
/concrete/images/icons/filetypes : emptied this folder completely, keeping the empty folder (3.6MB);
/concrete/js/tinyMCE : deleted this folder completely, folder included (10.8MB).
Inside the brackets is the space I saved with each one. I started out with 62.7MB - the size of the regular Concrete5 installation - and ended up with just 40.2MB.
The only major change I noticed was that I lost the WYSIWYG editor, replaced with a basic html editor when editing.
Can anyone think of any problem that I am not considering in doing this? Remember the goal I am set to achieve, wich I state in the opening of this post.