joaquinalcerro
So I am exploring Umbrella Apps to migrate a old application to have a better separation of concerns and of course I am trying to use the mix phx.gen tasks generators.
I am using Phoenix 1.4 and this version has the :context_app generator configuration options which work perfectly. But I have the following scenario:
apps
|
— db_service
|
— test
|
— test_web
I am trying to use the “test” application to host the context API. And I am trying to use the “db_service” application to use all the ecto stuff like schemas, etc.
So I have two questions:
- Should I separate the context from the schemas or
- Is there a proper command mix phx.gen.html [options] to do all this operation in one go
It is important to say that I can configure this scenario using the different command: mix phx.gen.html, mix phx.gen.context, mix phx.gen.schema but I still require some manual changes to make this work properly.
Thank you all for your feedback and suggestions.
Best regards,
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Error tracking, logs, APM, uptime and cron monitoring in one dev-friendly platform. Find and fix problems before your users notice.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #ai
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Producing high quality Elixir screencasts since 2017.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 2 to 1- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
joaquinalcerro
Thanks for your explanation and time.
Best regards.
easco
If I understand what you are trying to accomplish, then I would say “most definitely yes”. The context represents a logical chunk of functionality in your application - something that your application knows how to do. Say your application was for tracking shipments, then your context would be about how do you represent a shipment, what kind of operations can you do on shipments etc.
Your schema sits at the edge of your application and is concerned with how the elements of the context are represented in one particular type of storage (that being stored in a database). It’s a separation of concerns issue; you’re trying to separate what a thing is, from how that thing happens to be stored. If you wanted to get rid of a database and use a flat-file, or hook your application up to a 3D printer that generated plastic slabs where the data is encoded as if chiseled in stone, then you wouldn’t need the schemas - but the main logic of your application, the contexts, should still be valid.