3 ms·

> Setting up a new application on IIS or a new web server to scale is a mare. I disagree. With octopus deploy I can add a step, set a package and hostname, an

> Setting up a new application on IIS or a new web server to scale is a mare. I disagree. With octopus deploy I can add a step, set a package and hostname, and press a button, and have a new deployment of a new api or website in IIS pushed out to how ever many servers currently exist in a few minutes. There are many ways to manage deploying services, and scaling, without K8S or containers in general. While I could setup a new Octopus Deploy quickly, it would be like you setting up something in AKS. We are both good at the tools we know. But saying my way or your way is wrong - is the thing thats wrong.

boloust 4y ago
That is very interesting, I'd love to know more about how this works. - How does it decide which servers to deploy to? - Does it scale up the number of servers if the deployment is too large? - What happens when a server dies?
- philliphaydon 4y ago
  Well I guess it all depends on your setup. Servers get have a tentacle which has an environment and tag. So you could say a server is test environment and tagged with main-web-app. While another server is production with the same tag. You promote a package from test to production. You configure your setup to say a package is deployed to a server tagged main-web-app. Octopus is an orchestration tool so isn’t responsible for scaling up. But in AWS with an autoscale group you can configure Octopus to auto detect a new server tag it and deploy. Part of the deployment would add it to the load balancer. As a side note you can deploy containers using octopus too. Tho I’ve never found a reason to use containers in production yet.
mountainriver 4y ago
We’ll see if octopus deploy is around in 10 years
- philliphaydon 4y ago
  https://octopus.com/blog/insight-investment https://octopus.com/blog/insight-investment I would say they will be.
  - mountainriver 4y ago
    wow what a track record that investment firm has, jfrog lol

boloust 4y ago

That is very interesting, I'd love to know more about how this works. - How does it decide which servers to deploy to? - Does it scale up the number of servers if the deployment is too large? - What happens when a server dies?

philliphaydon 4y ago
Well I guess it all depends on your setup. Servers get have a tentacle which has an environment and tag. So you could say a server is test environment and tagged with main-web-app. While another server is production with the same tag. You promote a package from test to production. You configure your setup to say a package is deployed to a server tagged main-web-app. Octopus is an orchestration tool so isn’t responsible for scaling up. But in AWS with an autoscale group you can configure Octopus to auto detect a new server tag it and deploy. Part of the deployment would add it to the load balancer. As a side note you can deploy containers using octopus too. Tho I’ve never found a reason to use containers in production yet.

mountainriver 4y ago

We’ll see if octopus deploy is around in 10 years

philliphaydon 4y ago
https://octopus.com/blog/insight-investment https://octopus.com/blog/insight-investment I would say they will be.
- mountainriver 4y ago
  wow what a track record that investment firm has, jfrog lol