A crash course; probably not. But self-education. Sure.
It worked for me.
Before I started programming professionally I was a waiter. I had some college education in an unrelated field (though there are parallels) and I needed things to change.
Where you're coming from, you probably won't make much considering what you may make now. Be prepared to work on your craft before you start seeing a difference. The real money in development comes from experience, not just the tech stack. Someone who really knows their mainframe technology can still make good money in 2016. Because their time works harder for their company.
Once I got in with development, and proved some sort of worthy existence, I was fine. The hard part was getting in. Once I started I was able to negotiate and move up to a salary position (This field is contract-to-hire, predominantly, especially what you're interested in), move around and learn more.
I didn't stop there. Every time I felt like I was stagnant, I moved again; making my intentions obvious to employers about what I knew, where I was going, and what I wanted to do. This allowed me to get closer to the full-stack developer position I was going for.
But don't do it because it seems easier. It's very easy to get into a place that wants you to work forever, under extremely tight deadlines, and without much remorse. It's not always easier, and things do get under the gun. When Amazon is having issues with a site or app, you can bet your butt the developers behind it (contract or not) are working 24/7 to get it resolved, in extreme conditions and without seeing their families. The trick is finding the sweet-spot. Sounds like work-life balance is important to you, and that's always important to remember when considering potential positions.
Also be prepared to teach yourself until you retire. In Web development (or Mobile Apps, etc.) you must always keep up with the technology. And boy does it change. A lot. Be prepared to use almost nothing from one year to the next. The experience really comes in problem solving; not knowledge of one technology over another.
Instead focus on what you want to do, find the foundation of how that works/how it's built and start building. Without and work experience you're worth nothing, but showing someone how you make something, how you solve problems, and your knowledge of the foundation which you can only learn by doing; is where real employer interest comes from.
For web development there's tons of resources online. It's up to you to harness them. When I was cutting my teeth on it, I used CSS-Tricks, Udemy, Code Academy, Treehouse, and StackOverflow. As well as 100,000+ google searches.