Hey Jeffrey, you have a great product. I notice more and more you venture away from Laravel to cover more general PHP, Javascript, Vue and with the Laravel products you cover server management and deployment as well as IDE's and general coding practices.
Any chance you'll go over Docker or more general container approaches? Or maybe Route 53 from Amazon, or any of Amazon services?
Well there is a library out called [Laradock] (https://github.com/LaraDock/laradock) it's really simple to use. I use laradock when I need to use Mongo DB or any other databases.
Hello there! @BENderIsGr8te .
I really like the Docker image called Laraedit (https://github.com/laraedit/laraedit-docker). It's way more simpler than Laradock, and of course, you can easily extend it to fit your needs.
Even when from a "Docker point of view" Laradock separates all responsibilities as you are supposed to do, I think that is an overkill. Sometimes you just need something that is easy enough to get started.
If you need any help setting this up, please just ask ;)
Howdy! I know this is a tad old, but I'm building a docker series right now at https://shippingdocker.com.
If you sign up for the list you'll get a course on getting up and running with docker in dev with a multiple container setup (building the containers, using them in dev). You can actually find it here directly, but if you give your email by signing up, you'll get some other videos as well and I'll be able to let you know when the real thing is launched.
I'm also starting another small free course that expands on using day to day stuff in dev with docker!
The final series itself will cover production stuff!
I was fighting with docker until I discovered laradock as well: https://github.com/LaraDock/laradock it works really well on both Windows and OSX simple to configure and run.
Laradock works fine, but there is too much hidden complexity there. Honestly, I feel like Docker wasn't really designed for use in throwaway projects. Better to compose containers specifically for the task at hand.
I started using Docker the other day and what I find myself doing is just using Vagrant when I feel like writing my own docker-compose.yml is too much of a bother. "One size fits all" solutions are never elegant, but in Vagrant they are much easier to read and debug.
@fideloper provides great tutorials, by the way. You'll probably need to add nginx proxy to the suggested setup (for virtual hosts and the like) and you'll be ready to work your way up from there.
I've recently created a yeoman generator to simplify the process of creating a docker-compose file for a Laravel project. You can choose which containers to create when running the generator.
I started using docker on my projects since the release of "Docker for Mac". Since then I found myself copy and changing configuration files over and over. So I decided to create a yeoman generator to assist me on that job.