0

With TDS, I can set a non-local URL as my target website, leave the deploy folder blank, and do a "sync with Sitecore" just fine to push items. But it says I need a folder specified if I want to use the "Deploy" option instead. Is there any way to do ad-hoc remote deployments through Visual Studio?

  • First concern would be you need tds service in the remote server I.e. /website/_dev/tds service.asmx. Which is not ideal for cm or cd servers. Only development or equivalent env can have this service. – Balaji Kuppuswamy Mar 2 '17 at 19:28
  • That's present, I set up Visual Studio on the dev server and did a sync/deploy locally. So now I want to take the next step. It just seems odd I can sync but not deploy remotely. – Ken McAndrew Mar 3 '17 at 0:28
  • You mean, TDS +VS in dev server & able to sync with dev instance ? if that is the case would like to know Sitecore URL provided ? Please note that since you are in dev server you specific local binding URL (as mentioned in host file) & its deployment folder as <path>/website. – Balaji Kuppuswamy Mar 3 '17 at 6:42
2

There are a few options here (specifically for TDS). I haven't listed non-TDS options like doing MS Deploy packages or Visual Studio publish, since the question is specific about TDS remote deployment.

  1. UNC SHARE: You can setup a UNC share on your target server and then set the deploy folder to that network path (e.g. \MyServerName\Website). If you use that approach, make sure you lock the security down on that share.
  2. Sitecore Package Deployer: The Hedgehog Sitecore Package Deployer (https://www.teamdevelopmentforsitecore.com/Blog/sitecore-package-deployer) can be installed on your target instance and install packages for you. Generate packages with your items and files and then deploy to the secure 'Data' Folder that you specify during your configuration. The deployer will install for you.
  3. Team City: My preference is not to do deployments directly from the developer machine and to put things through Continuous Integration. Set up the UNC share, but lock it down so only the TeamCity server/user can access it. This is more secure than allowing all devs access to the server. Then let TeamCity do your deployments for you.

.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.