Publishing and different environments
Posted: September 29th, 2014, 3:46 pmHello everyone,
I'm curious to what kind of control I have in terms of setting up publishing rules with different environments in mind. I am working on a project that is obviously php based and developed by another company, so I don't have much control over the project other than making small adjustments here and there (otherwise upgrading becomes a nightmare).
Under a few subdirectories it has a config.xml file. /www/blah/blah/blah/config.xml for example. This file dictates the URL of the API it will communicate with as well as other settings. We have three environments that we work with. PROD, QA and DEV.
With the publish feature I can already deploy to the three environments which is quite nice, but I can't include the config.xml file in the publish. What I would like to do is have three config.xml files in the project:
Based on the publish profile I use I would like it to publish the corresponding config file and rename it to config.xml. Is this something I could ever hope to achieve with the publish feature? I feel as if there is a lot of power behind the .phpproj file that I haven't been able to tap.
Thanks
I'm curious to what kind of control I have in terms of setting up publishing rules with different environments in mind. I am working on a project that is obviously php based and developed by another company, so I don't have much control over the project other than making small adjustments here and there (otherwise upgrading becomes a nightmare).
Under a few subdirectories it has a config.xml file. /www/blah/blah/blah/config.xml for example. This file dictates the URL of the API it will communicate with as well as other settings. We have three environments that we work with. PROD, QA and DEV.
With the publish feature I can already deploy to the three environments which is quite nice, but I can't include the config.xml file in the publish. What I would like to do is have three config.xml files in the project:
- configPROD.xml
- configQA.xml
- configDEV.xml
Based on the publish profile I use I would like it to publish the corresponding config file and rename it to config.xml. Is this something I could ever hope to achieve with the publish feature? I feel as if there is a lot of power behind the .phpproj file that I haven't been able to tap.
Thanks