Centralised concrete/ directory
Permalink
Hi there
I'm with hostgator.com at the moment using addon domains to host multiple websites running C5 from 1 hosting account. They have a 100k inode 'soft limit' (past this they don't back files up), and a 250k hard limit (that I've already broken, they issue warnings past this which I seem to have avoided).
Deleted some files (eg files/tmp directory inside of my C5 websites) and got my inode count below 250k.
However I figure that if I can get all my C5 sites runnning off one concrete/ directory (one centralised core) then it would reduce inode count as I wouldn't have several concrete core directories with about 3.5k of files in them each time.
Any ideas how I can do this?
Thanks!
I'm with hostgator.com at the moment using addon domains to host multiple websites running C5 from 1 hosting account. They have a 100k inode 'soft limit' (past this they don't back files up), and a 250k hard limit (that I've already broken, they issue warnings past this which I seem to have avoided).
Deleted some files (eg files/tmp directory inside of my C5 websites) and got my inode count below 250k.
However I figure that if I can get all my C5 sites runnning off one concrete/ directory (one centralised core) then it would reduce inode count as I wouldn't have several concrete core directories with about 3.5k of files in them each time.
Any ideas how I can do this?
Thanks!
http://www.concrete5.org/documentation/how-tos/developers/setting-u...
Edit: I myself have one centralized installation on a windows environment and I must say the upgrade process alone makes it worth the trouble setting this up.