<< Part 2: MSBuild and deployable packages Part 4: Continuous builds with TeamCity >> In the first two parts of this series we got config transforms working and the web app successfully bundled into a nice self-contained deployable package. Next up: get the thing to publish. For the most part, the vast majority of web app deployment has historically been done by pushing the entire site out over either UNC or FTP, a practice which has a series of fundamental shortcomings that set deployment up for potential failure. To begin with, by default neither protocol is encrypted. Yes, there’s SFTP and FTPS but it’s not often you see these applied, particularly not as a...
I usually run private workshops around these, here's the upcoming public events I'll be at:
- DDD: 3 Dec, Brisbane (Australia)
- Workshop: Hack Yourself First: How to go on the Cyber-Offence: 16-17 Jan, London (United Kingdom)
- NDC London: 18-20 Jan, London (United Kingdom)
- Workshop: Hack Yourself First: How to go on the Cyber-Offence: 25-26 Jan, Leuven (Belgium)
- ZIONSECURITY Conference: 27 Jan, Leuven (Belgium)
- Here's how I verify data breaches
- When a nation is hacked: Understanding the ginormous Philippines data breach
- The world needs more stupid security researchers – join me!
- It’s time that you – the vulnerable human – brush up on your social engineering skills with Pluralsight
- How I optimised my life to make my job redundant