"Running from the update folder" ?
Permalink
Ok so in the this threadhttp://www.concrete5.org/index.php?cID=94104...
You can see reference to a question about running from the update folder. Can anyone explain to me what is happening here once you have done an "easy upgrade"? Are you using the files in the concrete folder or in the update folder?
You can see reference to a question about running from the update folder. Can anyone explain to me what is happening here once you have done an "easy upgrade"? Are you using the files in the concrete folder or in the update folder?
That being said, it is my opinion that the core files transferred to /updates during each new upgrade should only include any changed core files, not an entire install of concrete5 again. This would cut down on space requirements.
However, I'm not part of the core team, so they may have a better reason for it. Eventually, you have the potential to have many releases that each copy the entire structure and files of concrete5. It's like having 5 actual installs of concrete5 when maybe only 10% of the core files actually changed.
It would be nice if one of you find core gents could explain this to us?
However, I'm not part of the core team, so they may have a better reason for it. Eventually, you have the potential to have many releases that each copy the entire structure and files of concrete5. It's like having 5 actual installs of concrete5 when maybe only 10% of the core files actually changed.
It would be nice if one of you find core gents could explain this to us?
Thanks Lucas. So do the core files in the concrete folder server a purpose once you have updated?
As far as I can tell they don't serve a purpose unless you want to roll back the upgrade.
This allows for easier rollbacks in case the update does something funky to your site.
You would still house any core modifications within your root directory as usual. (Not within /concrete or /updates)