Home → Questions →

How to deploy same Artifact twice in the same box

• Edit

Gopi

20 Jul, 2016 03:32 PM

Hi,

I would like to deploy the same artifact twice with different value (for example different port and site name) on the same box. If I to do it just override the first one. Is there a right way of doing this?

Thanks,
Gopi

1. 1 Posted by leecheneler1 on 20 Jul, 2016 10:06 PM

   

   A little more background:

   We have a project, 1 db, 1 rest api, 1 website.

   The db is deployed to db server, rest api to one webserver, then the website is a little more particular.

   What we'd like to do is setup the website deployment so that we can deploy it multiple times to the same webserver on the same iis at the same time. So we have say 2 instances of it, one on port 80, the next on port 8080. Then if we want to add another we just add little more config specific to the next one and put that on port 8081 on the same server, same iis.

   Currently we use the deployment agent to pull the deployment to the machine. Our current setup pulls the first website, but then it pulls the second website directly over it. Any thoughts on how we could achieve this? It's for a dev environment, so we just need short and simple, not bullet proof. but it being quick and easy to deploy a new instance is key as its basically for whenever a team needs an instance spun up for them, we need to be able to give it them quickly. Then when an update gets rolled out its rolled out to them all at the same time without anyone caring.

   :) Thanks in advance!

   • Edit

2. 2 Posted by Ilya Finkelshte... on 21 Jul, 2016 09:46 AM

   

   Hi Lee,

   You can create 2 environments with the same environment assess key (which should be the same as deployment agent is using) and different following settings:
   site_Id, site_name, application_name, application_path, apppool_name, bindings
   After this you can choose what environment to deploy to.

   Another option is to have the same environment but with the different setting in appveyor.yml like this:
   deploy:
   - provider: Environment
     name: test-pc
     site_name: www.site-to-deploy.com
   - provider: Environment
     name: test-pc
     site_name: www.site2.com

   Second solution will work with deployment from build. However advantage of first solution (2 different environments with the same access key), is that it will work from UI too.

   Thank you,
   Ilya.

   • Edit

3. 3 Posted by Gopinath Sabapa... on 21 Jul, 2016 03:31 PM

   

   Hi Ilya,

   Cool. Thanks for the help.

   Thanks,
   Gopi

   • Edit

4. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 02:07 AM.