Hi all,
I'm starting to look at implementing best practices for releasing software to a clients website. Well anything is better than the current half baked approach.
This is a small dev team with frequent releases.
I've done this in a number of ways over the years but would be interested in how you guys have approached it, would be really interested in experiences with IIS, ASP.NET MVC, SQL Server environment.
Ideally I want something that automatically deploys to test or live. I want to reduce the amount of manual intervention.
I also want to minimize the down time of the site. I know this isn't always possible for example if database changes are involved. But I'm thinking of having two live sites one active the other inactive. So changes can be released to the inactive, testing to ensure all is ok then swap the active for inactive.
Perhaps a pre-production server may be an idea.
Any ideas, tools that you recommend or questions are welcome
Cheers
I'm starting to look at implementing best practices for releasing software to a clients website. Well anything is better than the current half baked approach.
This is a small dev team with frequent releases.
I've done this in a number of ways over the years but would be interested in how you guys have approached it, would be really interested in experiences with IIS, ASP.NET MVC, SQL Server environment.
Ideally I want something that automatically deploys to test or live. I want to reduce the amount of manual intervention.
I also want to minimize the down time of the site. I know this isn't always possible for example if database changes are involved. But I'm thinking of having two live sites one active the other inactive. So changes can be released to the inactive, testing to ensure all is ok then swap the active for inactive.
Perhaps a pre-production server may be an idea.
Any ideas, tools that you recommend or questions are welcome
Cheers
Comment