Home / Companies / Octopus Deploy / Blog / Post Details
Content Deep Dive

Changing website port on each deployment

Blog post from Octopus Deploy

Post Details
Company
Date Published
Author
Paul Stovell
Word Count
379
Company Posts That Month
6
Language
English
Hacker News Points
-
Post removed?
No
Summary

Paul Stovell discusses a method for managing multiple deployments of a website in a testing environment by using port numbers derived from the release version. By leveraging a PowerShell script, the process calculates a port number for each deployment using the modulo operator on the version's build number, allowing for the retention of a specified number of recent deployments. This approach ensures that older versions remain accessible even after new ones are deployed, with configurations made in the IIS feature of the package step. The port number is stored as an output variable, which can also be used to notify testers via email about new releases and their corresponding port numbers, offering an efficient solution for managing deployment environments.

Trends Found in this Post

No tracked trend matches for this post yet.

Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.