I've just installed Courier on two testing sites on the same server box (WinServ08 x86, in an Active Directory environment), with different hostnames, just so we can get familiar with Courier and how to use it to deploy from dev to staging/live.
I just have a couple of questions regarding the setup:
Licensing on domain wildcards - the hostnames of the site/s in question are "umbracocourier2.sub1.demo.ourdomain.com" and "umbracocourier3.sub1.demo.ourdomain.com". I tried getting a license for ourdomain.com so that (ideally) we could use a single license file to manage staging/live environments (we have Umbraco running in a cluster for a number of sites as well as lots of individual instances for development, testing and staging). However, Courier came back stating that the license was invalid. Many thanks to Per for sorting this - however, the wildcard subdomain licensing only seems to apply to a first-level subdomain (mysubdomain.ourdomain.com) - is this a bug or by design?
Moving content - it's great to be able to do this, however, without creating local packages to install on the receiving site, is there a way of moving doctypes, macros et al using Courier? If not, is it planned for a future release? And if not, are there API methods for programatically creating packages based on the content of the site? The reason I ask is that we're trying to automate our build process as much as possible to reduce headaches and time to deployment and this would be awfully handy, to be able to automate doctype and macro shunting from dev to staging.
Courier and document types
Hi guys,
I've just installed Courier on two testing sites on the same server box (WinServ08 x86, in an Active Directory environment), with different hostnames, just so we can get familiar with Courier and how to use it to deploy from dev to staging/live.
I just have a couple of questions regarding the setup:
Just discovered the API methods for auto-packaging - unless we go for MSBuild-based stuff this'll do nicely :-)
is working on a reply...