The update process of concrete5

Permalink
Hi!

I just looked at the file structure of one of my sites. I have upgraded it and now I saw that inside the "update"-folder is a complete version of the next version of concrete5.

Am I to understand that every time you do an automated upgrade the new version resides in the "update"-folder and the main core files from the old version is left on the server? The site just point to the new version in it's own map?

If so isn't that a bit wast of space on the server?

/Mr Lindau

 
adajad replied on at Permalink Best Answer Reply
adajad
Yes, that is as designed when you are doing automatic updates. Mostly because you will have something to fall back on if something fishy happens.

There will be some wasted space after some updates, and if you want to keep the total used space to a minimal I suggest you do manual updates according to method 2 in this how-to (which is what I do on all my sites): http://www.concrete5.org/documentation/how-tos/developers/manually-...
MrLindau replied on at Permalink Reply
Thanks for the suggestion. I've updated 3 sites now and they all work fine and deleted numerous updates that just took up space. =)

Tack för hjälpen!

/Mr Lindau
adajad replied on at Permalink Reply
adajad
Easy, right!

Inte visste jag att du satt bara 12 min ifrån mig. :D
frz replied on at Permalink Reply
frz
Yeah but isn't it awesome that you can have multiple cores and the
upgrade process is basically switching a pointer between them and
running whatever needs to happen to the database? Makes it really easy
to keep your overrides clean, makes it easy to keep track of whats
going on. Plus hard disk space is cheap. We're talking about 30megs
here or so.

That being said, feel free to delete old ones after a successful upgrade.

best wishes

Franz Maruna
CEO - concrete5.org
http://about.me/frz
MrLindau replied on at Permalink Reply
Yes it is awesome, now that I know how it works ;)