Good point and a nice trick, I love it ![]()
Yes, I didn’t envision for this to support different patterns than on_boot. It would be nice to have a bit of more structure, but I guess what @hubertlepicki suggests is a solid suggestion which doesn’t require any additional mechanisms, other than on_boot. I could just delegate to the desired module myself, and structure my code there, or I could use your approach and provide the app boot parameters in on_boot. I think I’d be fine with either.






















