Thanks! Tried to clarify that.
A few other thoughts before I let this go:
@pfaffman: one source of confusion is that you seem to be implying that the changes made to the default postgres (and probably redis) configurations by the
launcher script are also made during development. I don’t see where that happens—at least not the official native macOS guide. So, while these edits are probably important for production deployments, they don’t seem to be required to set up a working development database and get all of the tests passing.
@sam: the performance of this approach could be further improved by using the native postgres that
asdf will install and pin to the project for you, since then its IO is also outside of a container. (I would hope that Redis isn’t super IO bound…) I decided not to do this since it adds an extra command to the startup process, but it’s definitely possible. As noted above, this postgres would not have the deep customization done to prepare the production data container, but that doesn’t seem to be strictly necessary for development. At that point you’d just need to install redis—which sadly
asdf won’t do without brew.