tag:blogger.com,1999:blog-3897055.post1118551169469552803..comments2024-01-23T16:56:05.805-05:00Comments on Nuno Linhares: Manually configuring a Tridion 2011 .NET Content Deployer InstanceNunohttp://www.blogger.com/profile/10125817747610678434noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-3897055.post-4942377457152722162016-01-27T13:51:30.590-05:002016-01-27T13:51:30.590-05:00Another Deployer Configuration Tip
To grant the de...Another Deployer Configuration Tip<br />To grant the deployer write access to the target website with PowerShell<br /><br />$IncommingPath = "F:\WebContent"<br />$Acl = Get-Acl $IncommingPath<br />$Ar = New-Object system.security.accesscontrol.filesystemaccessrule("IIS AppPool\HTTPUpload_Live","FullControl","ContainerInherit, ObjectInherit", "None", "Allow")<br />$Acl.SetAccessRule($Ar)<br />Set-Acl $IncommingPath $AclChris Millshttps://www.blogger.com/profile/16616855966344881366noreply@blogger.comtag:blogger.com,1999:blog-3897055.post-10056521473233620262013-08-19T20:30:53.587-04:002013-08-19T20:30:53.587-04:00Hi
I have configured IIS deployer and i can acces...Hi<br /><br />I have configured IIS deployer and i can access my httpupload.aspx page in browser, logging says "Deployer Started", that means deployer is configured correctly. When i publish my page through CMS, it keeps on showing "Waiting for publish", Content publishing service is also running, nothing logged in event viewer, nothing logged in Tridion logging file.<br /><br />Can anybody help?Shafaqat Alihttps://www.blogger.com/profile/03898291848817253019noreply@blogger.comtag:blogger.com,1999:blog-3897055.post-1544892357798585312013-05-06T06:48:56.673-04:002013-05-06T06:48:56.673-04:00We need to provide it the necessary collections an...We need to provide it the necessary collections and settings to run as a tridion http example or material deployer that can agree to information we post to it.<br />Lionel Stevenshttp://amoskramer.wordpress.com/2013/05/03/net-development-is-a-worthwhile-option-for-many-software-developers-today/noreply@blogger.comtag:blogger.com,1999:blog-3897055.post-5483092859506217852012-11-22T08:28:47.433-05:002012-11-22T08:28:47.433-05:00Also need file 'Tridion.ContentDelivery.Intero...Also need file 'Tridion.ContentDelivery.Interop' from the folder 'Content Delivery\roles\upload\dotNET\dll\x86_64'RobertChttps://www.blogger.com/profile/14753443953233306219noreply@blogger.comtag:blogger.com,1999:blog-3897055.post-61180115801695865972011-11-12T01:28:10.381-05:002011-11-12T01:28:10.381-05:00One more tip on the license files and configs, esp...One more tip on the license files and configs, especially for Tridion customers -- be careful not to publish (.NET deploy) license and/or config files from your local machine and/or development server to other environments.<br /><br />You may have a separate content delivery (CD) license from the CMS if you're just developing for .NET websites.Nivlonghttps://www.blogger.com/profile/06783255433284043555noreply@blogger.comtag:blogger.com,1999:blog-3897055.post-53657154242356554622011-11-11T20:09:56.355-05:002011-11-11T20:09:56.355-05:00I've seen setups with previous versions of Tri...I've seen setups with previous versions of Tridion (R5.3) use publishing via the local file system on internal servers and HTTP for production (into the fire-walled DMZ). The rationale indeed was security.<br /><br />There may be a slight maintenance trade-off with mixing the publishing protocol methods.<br /><br />The craziest Tridion "legend" I've heard of was deployment by van and CD. It was actually by file system, but a courier would drive the fan to the remote destination with compact discs in hand and load the publishing transaction by dropping them off in the incoming folder. Myth? Possibly, but possible with the right settings.Nivlonghttps://www.blogger.com/profile/06783255433284043555noreply@blogger.comtag:blogger.com,1999:blog-3897055.post-2415751339080225002011-07-29T08:35:16.799-04:002011-07-29T08:35:16.799-04:00For my own test/dev environments: yes, since it gi...For my own test/dev environments: yes, since it gives me the flexibility to add more deployers on the same machine with different configurations.<br /><br />In production environments, it mostly depends on the security requirements. FTP or SCP data transfers will in principle be faster, but they're not as "firewall-friendly" as HTTP(S), so I end up seeing a lot of HTTP deployers in large companies.<br /><br />I guess in the end it is really up to your requirements. As said above, this is my preferred deployer for <b>my own</b> environments.Nunohttps://www.blogger.com/profile/10125817747610678434noreply@blogger.comtag:blogger.com,1999:blog-3897055.post-62628654371939482462011-07-29T03:27:26.741-04:002011-07-29T03:27:26.741-04:00Would this HTTP(S) deployer be your preferred opti...Would this HTTP(S) deployer be your preferred option over FTP all things considered?Neilhttps://www.blogger.com/profile/03452143351381121422noreply@blogger.com