3 ms·

> It's more from a sense of confusion: Should I go for an umbrella app where Phoenix is just one app that communicates with others? Or something that is primari

> It's more from a sense of confusion: Should I go for an umbrella app where Phoenix is just one app that communicates with others? Or something that is primarily a Phoenix app (as the book suggests, IIRC)? I'm obviously not Chris, but this is something that's been discussed in the community and the way it's ended up is that you have an Elixir application, not a Phoenix application. The way to treat it correctly in most cases is to have a Phoenix app be a part of an umbrella project where Phoenix handles the web component and very likely you'd have things like data and other services in one or more other applications inside the umbrella project. If you're curious about Elixir and Phoenix I highly recommend http://elixirforum.com/ http://elixirforum.com/ where you can find a great community for asking questions and learning more. Things like these come up every now and then and you get to be a part of the conversation and take everything in from both core members of the major projects to just other regular users.

mercer 9y ago
Thing is, if the right way to do it is an umbrella project, why does Phoenix 'take charge' by default (mix phx.new)? There's other similar stuff I ran into that I can't think of right now, but it's an example of what causes this confusion. I mean, I understand if the explicit goal of Phoenix is the provide an easy entry point for Rails devs, but I guess I'd like it if that was more explicit. All that said, I'm being nitpicky/pedantic. I love both Phoenix and Elixir, and the ecosystem. And yes, I've been enjoying the elixir forums. Do you happen to know if there's some way to get a decent mobile version?
- 59nadir 9y ago
  What do you mean by `mix phx.new` taking charge? $ mix new elixir_umbrella --umbrella $ cd elixir_umbrella/apps $ mix phx.new elixir_umbrella_web This should work just fine and it means that this phoenix application is a sub-application in your umbrella project. Likely you'd do a `mix new elixir_umbrella_cool_service` to handle DB and service stuff that is more about business logic. I can sort of see what you mean by Phoenix doing magic, because a lot of what you see on the surface looks like magic, but it's hard to really discuss these things when one can't pinpoint what the actual issue is. On the idea of rails developers having an easy time, I don't really think it's that big a part of the concept, to be honest. A rails dev expecting rails is going to drown in BEAM/OTP things anyway provided he isn't making the same postgres + web-server applications without any real value from the BEAM, so I don't think the idea is to really cater to that kind of thing anyway. I'm not a rails dev, so I can't really say what their feeling is.

mercer 9y ago

Thing is, if the right way to do it is an umbrella project, why does Phoenix 'take charge' by default (mix phx.new)? There's other similar stuff I ran into that I can't think of right now, but it's an example of what causes this confusion. I mean, I understand if the explicit goal of Phoenix is the provide an easy entry point for Rails devs, but I guess I'd like it if that was more explicit. All that said, I'm being nitpicky/pedantic. I love both Phoenix and Elixir, and the ecosystem. And yes, I've been enjoying the elixir forums. Do you happen to know if there's some way to get a decent mobile version?

59nadir 9y ago
What do you mean by `mix phx.new` taking charge? $ mix new elixir_umbrella --umbrella $ cd elixir_umbrella/apps $ mix phx.new elixir_umbrella_web This should work just fine and it means that this phoenix application is a sub-application in your umbrella project. Likely you'd do a `mix new elixir_umbrella_cool_service` to handle DB and service stuff that is more about business logic. I can sort of see what you mean by Phoenix doing magic, because a lot of what you see on the surface looks like magic, but it's hard to really discuss these things when one can't pinpoint what the actual issue is. On the idea of rails developers having an easy time, I don't really think it's that big a part of the concept, to be honest. A rails dev expecting rails is going to drown in BEAM/OTP things anyway provided he isn't making the same postgres + web-server applications without any real value from the BEAM, so I don't think the idea is to really cater to that kind of thing anyway. I'm not a rails dev, so I can't really say what their feeling is.