Moving from development box to live website

Next topic

Author	Message
Mark Irvine	Wednesday 21 January 2004 10:37:04 am Hi, I'm trying to work out if ezpublish will allow me to develop a website on a development machine, and then move the updates to a live website. I can pretty much see how to do this on a one off, first time basis. i.e copy the directory tree, then copy the database. But what about later, as the live website content gets updated, and I want to change the design by, for example,adding a new section with new templates etc? Can I change the design on the development, then move the design changes to the live site without loosing content? I obviously can't just copy the entire database this time, I'll probably lose any new content, correct? Is anybody using ezpublish in this way? What I don't want to do is make design changes on the live website. Any ideas/feedback would be appreciated. Thanks, Mark
Shurbann Martes	Thursday 22 January 2004 2:15:39 am Hi Mark, Design changes (look and feel of your site) has nothing to do with the DB, where mostly the content sits. Two things are important here: 1. the override.ini (override setting of site A: settings/siteaccess/site_A/override.ini.append) and maybe other setting files (for example image.ini.append if you have changed the image sizes in the new look etc.) 2. the design directory (override templates of site A: design/design_A/), where you have the stylesheets, images and templates When you change the look on your development server and it's working allright. The only thing you have to do is, backup the files you're going to change on the production server. And overwrite them with the new ones. In the database there's nothing stored that has something to do with the look of your site. So don't bother doing overwriting the whole DB to the production server, as you might only be losing new contents. The crucial thing here is to backup everything you're going to change. Hth, -Shurbann
Tore Skobba	Thursday 22 January 2004 2:59:11 am Hi Regarding this: >Design changes (look and feel of your site) has nothing to do >with the DB, where mostly the content sits. > Well what about about adding new classes which I often do. The definition of classes are stored in the database. However, I am gonna check out the packages system. Think that might offer an solution, but I do think it require one of the latest version, i.e. Ez 3.3-X Cheers Tore
Shurbann Martes	Thursday 22 January 2004 6:41:24 pm Yup you're right changing a class will change the DB. But till I don't think classses are part of a site feel and look. In my case everytime I add a new class on the development server, I make sure I do the same on the production server. I mean how many times are you going to change or make a new class after launching your site? (this is not THE time-consuming factor, IMHO) -Shurbann