hey all dory users, esp @FreedomBen , since we need a reliable local development hub solution, and dory hasn't been updated in ages, i'm thinking of picking it up development-wise (adding the localhost hack as a configurable option, updating the dnsmasq dependency, harmonizing it with the latest docker desktop and m1 macs), unless someone found a better solution.
so -- is there a better solution for what we use dory for (making certain images available under a simple .docker hostname, wildcard proxying, making the images communicate with each other using the same .docker domains on the docker-inside network)? or is there enough interest in keeping dory alive which i'm willing to take over?
hey all dory users, esp @FreedomBen , since we need a reliable local development hub solution, and dory hasn't been updated in ages, i'm thinking of picking it up development-wise (adding the localhost hack as a configurable option, updating the dnsmasq dependency, harmonizing it with the latest docker desktop and m1 macs), unless someone found a better solution.
so -- is there a better solution for what we use dory for (making certain images available under a simple .docker hostname, wildcard proxying, making the images communicate with each other using the same .docker domains on the docker-inside network)? or is there enough interest in keeping dory alive which i'm willing to take over?