Hi! I'm Rohan, a Full Stack Software Engineer, with a background of working with Deep Learning and AI, who loves to use his skills to create products that are at the intersection of all of these!
I personally do this weird bit where I always make sure that development is 'possible' in docker, I make sure that everything spins up with a single command with docker-compose.
Then I expose the DB Container through a port and connect to it via my dev environment, or my IDE.
This means one could completely depend on docker if they choose to and partially depend on it if they want to.
I think this is the ultimate. You provide all the pieces so other devs can pick and choose the things they want to run locally. You dont have to work 100% in containers to get the benefits.
I personally do this weird bit where I always make sure that development is 'possible' in docker, I make sure that everything spins up with a single command with
docker-compose.Then I expose the DB Container through a port and connect to it via my dev environment, or my IDE.
This means one could completely depend on docker if they choose to and partially depend on it if they want to.
How do you do it? Can you link to some tutorials on how to have a good local dev workflow?
I think this is the ultimate. You provide all the pieces so other devs can pick and choose the things they want to run locally. You dont have to work 100% in containers to get the benefits.
I like this approach, thanks for sharing :)