> The _build folder contains all build artifacts for external dependencies and internal application code. This means that caching this folder is a pain.
Could you elaborate why is this painful? Is it the sheer size of the _build directory? Or you don't want to cache app code? Please note that e.g. heroku-buildpack-elixir caches the whole _build directory, however uses `mix compile --force` to compile the project - this makes sure that your app code is always recompiled (works in umbrella too) but the deps are only recompiled when they actually change. W dniu środa, 20 grudnia 2017 08:18:05 UTC+1 użytkownik José Valim napisał: > > > The deps.compile within an umbrella application actually compiles some of >> the internal applications. I would actually need to do: >> > > You can still use a Mix task to get the name of the umbrella applications > and figure out what you want to cache or not - or even have the mix task > doing the caching. It seems clear only relying on the file system is not > enough for you but I think you should focus on caching more > programmatically rather than expecting Mix to lay out the perfect directory > structure for you. > > We need a very strong reason to change the _build structure which has been > settled from before Elixir v1.0. > -- > > > *José Valimwww.plataformatec.com.br > <http://www.plataformatec.com.br/>Founder and Director of R&D* > -- 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 elixir-lang-core+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/b10702b2-fd09-4785-ac70-b719925ba90c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.