/concrete/packages folder
Permalink
I'm hoping someone who knows can advise on making use of the /concrete/packages/ to install add-on packages. Let me explain.
Firstly, we have centralised our C5 install using the symlink methods. Symlinked at the /concrete and /packages folders. So every C5 install makes use of the core c5 files and have access to some standard packages.
The issue comes when we want to tweak a package for a particular website. The files we want to tweak may be specific to the package itself, rather than those C5 looks for such as an edit.php. In these instances, creating the updated package-specific files in the root /blocks folder has no effect since C5 doesn't control their inclusion.
So as a work around, we are considering placing installed packages in the /concrete/packages folder (which is normally reserved for the C5 install itself), and if we need to update a package, we could replicate it in the /packages folder and make the tweak.
Have not tested this yet to ensure it will work as we expect. But would there be any drawbacks to using the /concrete/packages folder for general add-on installs rather than the /packages folder?
Many thanks for any response!
Firstly, we have centralised our C5 install using the symlink methods. Symlinked at the /concrete and /packages folders. So every C5 install makes use of the core c5 files and have access to some standard packages.
The issue comes when we want to tweak a package for a particular website. The files we want to tweak may be specific to the package itself, rather than those C5 looks for such as an edit.php. In these instances, creating the updated package-specific files in the root /blocks folder has no effect since C5 doesn't control their inclusion.
So as a work around, we are considering placing installed packages in the /concrete/packages folder (which is normally reserved for the C5 install itself), and if we need to update a package, we could replicate it in the /packages folder and make the tweak.
Have not tested this yet to ensure it will work as we expect. But would there be any drawbacks to using the /concrete/packages folder for general add-on installs rather than the /packages folder?
Many thanks for any response!
.
One work around I've thought of, is to symlink each add-on package rather than the packages/ folder itself.
Then have a script that checks all C5 accounts using the centralised install, and creates any symlinks to the centralised.
That way, if we want to tweak a package for just one website, then we can remove the symlink and copy the real package files there.
Seems like a little messing around, but shouldn't be too hard to write a script to keep the symlinks for each package synchronised.
Might be overkill, but would be great if C5 natively supported a third packages folder ;) -- where if the add-on package folder existing within it, then the add-on in the packages/ folder is ignored.
Then have a script that checks all C5 accounts using the centralised install, and creates any symlinks to the centralised.
That way, if we want to tweak a package for just one website, then we can remove the symlink and copy the real package files there.
Seems like a little messing around, but shouldn't be too hard to write a script to keep the symlinks for each package synchronised.
Might be overkill, but would be great if C5 natively supported a third packages folder ;) -- where if the add-on package folder existing within it, then the add-on in the packages/ folder is ignored.
No good to you if you need to make centralised updates to the your symlinked packages, but I don't think there is a perfect solution in this scenario.