Courier 2.1.1 (Removed 1.3 and installed 2.1.1 - licensed)
Both servers exist on the internal network, but accessing them via subdomain http names (ex. http://staging.domain.com) in the courier.config file.
Sometimes when deploying a file to the production server, IIS hangs for that site and requires me to restart IIS for that site to bring it back up.
Other times when a file is deployed/updated, it states that the file was successfully moved, but it isn't showing up on Production. Sometimes the link to it is there, but clicking on the link to it brings up an error because the page doesn't exist. When this happens on an update of an existing file, I have to delete the file on production and resend from staging.
Is there anything specific that I can look for to resolve these issues? Would it be possible (or even be helpful) to configure the courier.config file somehow without using the complete web address (http://production.domain.com as production.local somehow)?
This version of courier is so different from 1.3 and we had no problems like this with that version. I'm guessing there is something to do with the number/size of files dependancies being transferred in this new version that cause problems. I'm just lookign for any information I can find that might be useful in resolving these problems. Thanks!
Would it be possible to look into the sites you are trying to deploy, so I can get an idea of the data being transfered? courier stores a backup of the revisions you try to deploy in /app_data/courer/revisions, if I could get one of those zipped and sent to me, that would help alot.
Courier 2, is massively different with Courier 1, it has to take a lot of extra dependencies into acount, so it has some additional overhead. Especcially as there are 100s of ways you can structure your content / document Types / files, there can be areas where it will be inefficient or simply not work, the more scenarios we see from users, the more we can improve it.
Occaisonal freezing IIS on the server I'm deploying to with Courier 2.1.1
Both servers:
Sometimes when deploying a file to the production server, IIS hangs for that site and requires me to restart IIS for that site to bring it back up.
Other times when a file is deployed/updated, it states that the file was successfully moved, but it isn't showing up on Production. Sometimes the link to it is there, but clicking on the link to it brings up an error because the page doesn't exist. When this happens on an update of an existing file, I have to delete the file on production and resend from staging.
Is there anything specific that I can look for to resolve these issues? Would it be possible (or even be helpful) to configure the courier.config file somehow without using the complete web address (http://production.domain.com as production.local somehow)?
This version of courier is so different from 1.3 and we had no problems like this with that version. I'm guessing there is something to do with the number/size of files dependancies being transferred in this new version that cause problems. I'm just lookign for any information I can find that might be useful in resolving these problems. Thanks!
Hi Chris
Would it be possible to look into the sites you are trying to deploy, so I can get an idea of the data being transfered? courier stores a backup of the revisions you try to deploy in /app_data/courer/revisions, if I could get one of those zipped and sent to me, that would help alot.
Courier 2, is massively different with Courier 1, it has to take a lot of extra dependencies into acount, so it has some additional overhead. Especcially as there are 100s of ways you can structure your content / document Types / files, there can be areas where it will be inefficient or simply not work, the more scenarios we see from users, the more we can improve it.
you can get ahold of me at pph at umbraco . dk
Sure. I can get one of those to you. I'll email you to plan a send type. Thanks for your help!
Just as an update, this was fixed by upgrading to Courier 2.5.
is working on a reply...