We're using umbraco for multiple applications here at work. We have on in particular where we're really trying to automate our deploy processes between dev, test, live. I'm just wondering how that works in terms of packages?
We're mainly wondering how can you keep packages in source control when depending on environment their folder / files are in a folder of a different guid and their files are installed all around the install.. have you had any experience with that scenario?
can we just blow away the installed packages config in test and live and copy everything up (the db schemas are a manual upgrade of course but is there anything else we'd need to migrate up in terms of db where packages are concerned?)
Each package is different, but mostly they are just files/folders/dlls and config changes. Sometimes packages will affect the DB too (mostly additional tables).
As far as I know packages.config is just for listing the files so nothing to do with the packages running.
For example ImageGen & uComponents are part of our default build, so we just check the affected files into source control as normal.
Packages Version Control
Hi Umbraco Team,
We're using umbraco for multiple applications here at work. We have on in particular where we're really trying to automate our deploy processes between dev, test, live. I'm just wondering how that works in terms of packages?
We're mainly wondering how can you keep packages in source control when depending on environment their folder / files are in a folder of a different guid and their files are installed all around the install.. have you had any experience with that scenario?
can we just blow away the installed packages config in test and live and copy everything up (the db schemas are a manual upgrade of course but is there anything else we'd need to migrate up in terms of db where packages are concerned?)
Cheers,
Tom
Hey Tom,
Each package is different, but mostly they are just files/folders/dlls and config changes. Sometimes packages will affect the DB too (mostly additional tables).
As far as I know packages.config is just for listing the files so nothing to do with the packages running.
For example ImageGen & uComponents are part of our default build, so we just check the affected files into source control as normal.
Hope that helps a little.
Rich
I'm not sure what you mean about packages having different GUID's? I'm not sure that's possible.
How much would this package cost. - Casa Sandoval
is working on a reply...