Subscribe: Dan Wahlin's WebLog
http://weblogs.asp.net/dwahlin/rss.aspx
Added By: Feedage Forager Feedage Grade C rated
Language: English
Tags:
benefits docker  blog  developers  docker images  docker web  docker  images  lot  machine  net  new  people  wasn’t  web developers  web 
Rate this Feed
Rate this feedRate this feedRate this feedRate this feedRate this feed
Rate this feed 1 starRate this feed 2 starRate this feed 3 starRate this feed 4 starRate this feed 5 star

Comments (0)

Feed Details and Statistics Feed Statistics
Preview: Dan Wahlin's WebLog

Dan Wahlin



AngularJS, JavaScript, HTML5, jQuery, Node, ASP.NET, C#, XAML



 



Moving Blog to http://blog.codewithdan.com

Mon, 04 Apr 2016 09:00:00 GMT

(image) After many years hosting my blog at http://weblogs.asp.net/dwahlin I’ve decided to move over to a custom domain. I’ve really appreciated the hosting that Microsoft has provided and the excellent service behind the scenes by Neudesic. The existing blog and all of the posts will stay up but new posts will be at the URL mentioned below.

Why am I moving the blog you ask? First off, people have a real challenge spelling my last name (“Wahlin”) and it’s hard to remember “dwahlin” if you’re trying to go to the blog directly. Second, our new company website is going to be at http://www.codewithdan.com so I figured I might as well move the blog there as well. The company site will be released a bit later and we have a lot of great content planned for it. My wife came up with the “Code with Dan” concept based on feedback we’ve had from several clients over the years and felt that it’d be a lot easier to remember for people.

I may still post a portion of each blog post here at the old blog to gradually move people over, but if you have this blog (http://weblogs.asp.net/dwahlin) bookmarked you’ll want to change the bookmark to http://blog.codewithdan.com. Thanks!




New Pluralsight Course: Docker for Web Developers

Sun, 19 Oct 2014 17:08:00 GMT

How I Got Into Docker (and why you should too) One of the most exciting technologies that I’ve researched and used over the past year is Docker. That’s a pretty bold statement, especially since I enjoy working with a lot of different technologies, so let me share a quick story about how I initially got started with Docker and and my personal journey (if you’d prefer you can jump directly to the Docker for Web Developers Course). You may have heard the term “Docker” tossed around at work or online and wondered what it was…I know I did. I heard a few people mention it on Twitter a few years ago making claims like, “Docker provides a consistent way to deploy applications.” That sounded appealing but wasn’t enough to make me jump into it. I’ve worked in a lot of dev environments over the course of my career and have certainly run into challenges moving software between development, staging and production environments so the general promise of Docker certainly intrigued me. But, when it came down to it I only had so many hours in the day to research new technologies so I pushed it off. It kept coming up again and again though so I realized I needed to make some time to look into it more. Fast-forward a few more weeks and one night I decided to visit the Docker website and do a little reading on the features it offered. The additional features I learned about continued to interest me but at the time I felt like Docker was aimed squarely at SysAdmins which wasn’t that exciting to me - no offense to my SysAdmin friends. :-) It was also 100% Linux-based when it first came out and I wasn’t a “Linux guy” back then. I was super comfortable with Mac and Windows but “Linux” just wasn’t my thing. I put off looking into it more but decided to sign-up for the Docker Newsletter just to keep an eye on it and see if anything interesting showed up. I read a lot of great articles that listed some of the key features: As I dug in deeper I learned that Docker allows “Images” published up on Docker Hub to be used to create instances of running “Containers”. An image is a super efficient way to get a given framework (Node, ASP.NET Core, PHP, etc.), database servers, caching servers and much more up and running on your dev machine or even in production. What’s so cool about the Docker technology is that “Images” aren’t the same thing as the “Virtual Machine Images” you may have used before. In fact, Docker Images are very different from Virtual Machine Images as they’re typically smaller and more efficient to start and stop. A Docker Image isn’t a full OS as with Virtual Machines – it’s a layer that’s added onto a host OS so there are a lot of benefits that Docker Images bring to the table.  I’ll save that discussion for another post though. In the meantime, here’s a quick summation of Docker Images and Containers for you: This still sounds/looks rather SysAdmin-ish though right? That’s what I thought initially too. Let’s get to the good stuff that can impact you and your development projects. How Docker Can Help Web Developers (and many others) One day I saw an article in the Docker Newsletter that focused on a few key benefits that Docker offered to web developers. After reading it and thinking it over more I had one of those “light bulb moments” and thought, “Hey, this technology can be used to setup a consistent development environment quickly and easily! How cool is that?” What do I mean by that exactly? Let’s say that you need to get Node, MongoDB, nginx, Redis and possibly more up and running on your dev machine. In addition to getting these requirements all installed properly, you also have to worry about getting security, configuration and more in place. To top it off, everyone on your team needs to do the same thing on their machines. Do you all have the correct versions of the servers and frameworks installed? What happens in a month or two when a new version comes out for a server/framework that everyone decides to[...]