Refactor post start mix task operations orchestration #58
Description
The way the command is now, is too busy. There's too much scope within the file to a point where I forgot that environment variables were being loaded (by a custom thing that I did) instead of using something like dotenvy
This issue will be used as a mean to breakdown the scope of the mix task to see something akin to the following pattern:
- We have file modules responsible for an aspect of the container setup after mounting
- We have an orchestrator that's responsible for composing these flows together so that we run a single mix task
This time, we're going to need some docs to explain the pattern and what is expected in the future if we need to extend with more automations after the mounting so we don't have something similar happen again.