Ah sorry read too fast, you want to be able to run the phases before starting dependencies.
On 9 February 2017 at 19:27, James Fish <[email protected]> wrote: > Hi Isak. > > You should be able to use start phases without moving :applications to > :included_applications. Can you explain why moving an application to use > start phases without making other changes does not work? > > James > > On 9 February 2017 at 08:50, José Valim <[email protected]> > wrote: > >> This is an interesting idea, we would also need to sync this with >> releases. We are also trying another approach with Phoenix 1.3, which is to >> customize how Ecto or Phoenix works on your application start, before >> starting the repo or endpoint in your app. The advantage of doing so in >> your code directly is that it makes it clear that it is a runtime >> configuration. However, it would allow you to customize only what you >> explicitly start. >> >> >> >> >> *José Valim* >> www.plataformatec.com.br >> Skype: jv.ptec >> Founder and Director of R&D >> >> On Wed, Feb 8, 2017 at 11:41 PM, Isak Sky <[email protected]> wrote: >> >>> It would be great if there was an easy way to execute logic before any >>> application in the mix application list is started. >>> >>> I know about :start_phases in mix.exs/application, but this requires >>> that you take move applications from :applications to >>> :included_applications, then start them all yourself. >>> >>> I have also heard there are ways to do it for releases, but it would be >>> great to be able to do it in development as well the same way. >>> >>> If this feature was added, it would enable better ways to do >>> configuration. In the current situation, you are at the mercy of other >>> developers adding support for {:system} type tuples, if you want to use >>> that approach, for example. Some developers don't support it at all, some >>> support ones with 2 elements, and not with 3, or support it for some >>> configuration properties, and not for others (hi Ecto). Overall, it seems >>> like it is a little harder to reason about than it needs to be. >>> >>> This feature would enable a convenient escape. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "elixir-lang-core" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit https://groups.google.com/d/ms >>> gid/elixir-lang-core/20ea6bec-0e1e-44a3-881a-1561768fd6c2%40 >>> googlegroups.com >>> <https://groups.google.com/d/msgid/elixir-lang-core/20ea6bec-0e1e-44a3-881a-1561768fd6c2%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "elixir-lang-core" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit https://groups.google.com/d/ms >> gid/elixir-lang-core/CAGnRm4%2ByZ%2BoyKaoBLcr1R7FY8OWKF6ZV2 >> pgARD3U%2Bj8uJpuheQ%40mail.gmail.com >> <https://groups.google.com/d/msgid/elixir-lang-core/CAGnRm4%2ByZ%2BoyKaoBLcr1R7FY8OWKF6ZV2pgARD3U%2Bj8uJpuheQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "elixir-lang-core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/CA%2BibZ9-y_o-CEOQW7U7KZ55KaaDFY2OcudMUofhFeLLqgvsjUQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
