Categories
Posts in this category
- Automating Deployments: A New Year and a Plan
- Automating Deployments: Why bother?
- Automating Deployments: Simplistic Deployment with Git and Bash
- Automating Deployments: Building Debian Packages
- Automating Deployments: Debian Packaging for an Example Project
- Automating Deployments: Distributing Debian Packages with Aptly
- Automating Deployments: Installing Packages
- Automating Deployments: 3+ Environments
- Architecture of a Deployment System
- Introducing Go Continuous Delivery
- Technology for automating deployments: the agony of choice
- Automating Deployments: New Website, Community
- Continuous Delivery for Libraries?
- Managing State in a Continuous Delivery Pipeline
- Automating Deployments: Building in the Pipeline
- Automating Deployments: Version Recycling Considered Harmful
- Automating Deployments: Stage 2: Uploading
- Automating Deployments: Installation in the Pipeline
- Automating Deployments: Pipeline Templates in GoCD
- Automatically Deploying Specific Versions
- Story Time: Rollbacks Saved the Day
- Automated Deployments: Unit Testing
- Automating Deployments: Smoke Testing and Rolling Upgrades
- Automating Deployments and Configuration Management
- Ansible: A Primer
- Continuous Delivery and Security
- Continuous Delivery on your Laptop
- Moritz on Continuous Discussions (#c9d9)
- Git Flow vs. Continuous Delivery
Sat, 05 Mar 2016
Automating Deployments: New Website, Community
Permanent link
No IT project would be complete without its own website, so my project of writing a book on automated deployments now has one too. Please visit deploybook.com and tell me what you think about. The plan is to gradually add some content, and maybe also a bit of color. When the book finally comes out (don't hold your breath here, it'll take some more months), it'll also be for sale there.
Quite a few readers have emailed me, sharing their own thoughts on the topic of building and deploying software, and often asking for feedback. There seems to be a need for a place to share these things, so I created one. The deployment community is a discourse forum dedicated to discussing such things. I expect to see a low volume of posts, but valuables to those involved.
To conclude the news roundup for this week, I'd like to mention that next week I'll be giving a talk on continuous delivery at the German Perl Workshop 2016, where I'm also one of the organizers. After the workshop is over, slides will be available online, and I'll likely have more time again for blogging. So stay tuned!
I'm writing a book on automating deployments. If this topic interests you, please sign up for the Automating Deployments newsletter. It will keep you informed about automating and continuous deployments. It also helps me to gauge interest in this project, and your feedback can shape the course it takes.