Using Composer Path Repositoriess While Running PHP Apps With Docker Compose

In this week's episode I shared a little experience I had during the week where I didn't update my docker-compose.yml file to account for the fact that the path to a forked git repository was outside of my default Docker context, and how I quickly fixed it. Plus a tease for next week's episode covering JWTs, OAuth2, and OpenID Connect.
Docker Compose is an excellent way of deploying apps both on local development machines and to remote environments, but does it play nice with Composer path repositories. Yes. They sure do. In this week's episode I shared a little experience I had during the week where I didn't update my docker-compose.yml file to account for the fact that the path to a forked git repository was outside of my default Docker context, and how I quickly fixed it. 

Grab your favourite beverage, settle in, and please don't mind me meandering a bit here an there throughout the course of the episode.

Links from the episode
Want to grow your knowledge further?

Check out the books and courses below, where you can grow your web development skills in a very focused, very hands-on way.
Hosted and produced by: Matthew Setter.
Website: https://webdevwithmatt.com
Follow me on: Twitter and LinkedIn.

If you like the podcast, and want to support it, how about buying me a coffee?
★ Support this podcast on Patreon ★
Using Composer Path Repositoriess While Running PHP Apps With Docker Compose
Broadcast by