Centralization help
Permalink
We have four concrete5 websites over four different domains all on the same hosting account and they all use the same custom theme, copied on each domain.
We have read up on Centralization and it sounds like the perfect solution for updating our theme in one place -
http://www.concrete5.org/documentation/how-tos/developers/setting-u...
Brief
We need help and guidance in how to set up a centralised install for the core 'concrete/' files, and our custom theme & blocks.
In particular we need help with symlinks -
• What is the symlink syntax for the concrete,themes and blocks directory?
• Can symlinks be used when the site is on a subdomian?
• Where is the Smylink code added?
• Do we need to upgrade hosting account to include shell access?
(Hosting - we are using a heart internet reseller account)
Just looking for someone to help us set up the system and process and leave us with a detailed explanation of how to setup centralisation & symlinks for future projects / Sites.
Please PM me to start the discussion
We have read up on Centralization and it sounds like the perfect solution for updating our theme in one place -
http://www.concrete5.org/documentation/how-tos/developers/setting-u...
Brief
We need help and guidance in how to set up a centralised install for the core 'concrete/' files, and our custom theme & blocks.
In particular we need help with symlinks -
• What is the symlink syntax for the concrete,themes and blocks directory?
• Can symlinks be used when the site is on a subdomian?
• Where is the Smylink code added?
• Do we need to upgrade hosting account to include shell access?
(Hosting - we are using a heart internet reseller account)
Just looking for someone to help us set up the system and process and leave us with a detailed explanation of how to setup centralisation & symlinks for future projects / Sites.
Please PM me to start the discussion
Never heard of this before but sounds great. How does it work when you upgraded?
I do manual upgrades.
http://www.concrete5.org/documentation/how-tos/developers/manually-...
At the root I copy over the latest concrete core and append the version number to it. So I admit I do have one file structure that looks like this:
/concrete56
/concrete561
/concrete5621
From here I manually update the symbolic links in each sites directory to point to the version of Concrete5 I want to run.
http://www.concrete5.org/documentation/how-tos/developers/manually-...
At the root I copy over the latest concrete core and append the version number to it. So I admit I do have one file structure that looks like this:
/concrete56
/concrete561
/concrete5621
From here I manually update the symbolic links in each sites directory to point to the version of Concrete5 I want to run.
Does your hosting account provide ssh access? You'll need this to create the symbolic links. Symbolic links are created outside of Concrete5 and are created in your shell.
I have numerous sites running off of one concrete core and this is easy to setup.
I put the concrete core at the top level and append the version number to it so I can better keep track of it.
The directory structure looks like this:
/concrete5621
/www.siteone.com
/www.sitetwo.com
Inside /www.siteone.com create a symbolic link to the concrete core:
ln -s ../concrete5621 concrete
You can do something similar for your themes, blocks and anything else you want. I have one large site that has the files directory symbolically linked to an external disk.
Let me know if I've throughly confused you.
Cheers,
Anthony