[e1g]

Another cool feature could be to link up with Homebrew services. Redis/ES/nginx/etc are mostly installed through brew, and 'brew services' provides a convenient shortcut to status/restart/stop/view status of those apps.

Having Marathono popup function as a proxy for Homebrew-managed services would give me a single dashboard for my development daemons, including infrastructure and my own app codes.

[yliang]

Good idea. You could track the status of this feature at https://gitlab.com/marathono/marathono/issues/9

[toomuchtodo]

> Redis/ES/nginx/etc are mostly installed through brew

Consider using Docker/Docker Compose for this. It then becomes as easy as defining the image name and version, pulling it, and then starting the container. No brew, no version conflicts, it just works.

[e1g]

Absolutely, Docker makes these services easy to deploy. Unfortunately I'm the only one on the team using it - everyone else is deeply entrenched with Brew, hence I'm asking for them.

In defence of the team, the Docker value prop on macOS is fundamentally undermined by the broken shared volumes. Folders that are shared with the hosts are still unusably slow for larger projects, so we can't use them (docker-sync makes it better, but adds another layer of complexity). Further, a lot of tooling and IDEs still expect local files and a local interpreter for step-debugging. So if the files are on the host, and so is node/php, then docker adds no dev value for app-level work. CI, yes, local dev - not so much. From there, it's a slippery slope - if I already have app stuff on the host, might as well install infrastructure stuff too because it doesn't really change so why should I deal with another virtualisation layer. It'll be an uphill battle until Docker volumes work at native speeds on mac out of the box.