rob_marsh
Hi all,
I’m looking for some advice on how to structure an application I’m building. It should eventually contain an importer that runs daily and a Phoenix application to display the information. Seeing as both applications use the same data I decided to try out an umbrella application containing a “core library” that acts as a Data Access Layer whilst allowing the schema to be shared. The application hierarchy currently looks like the following…
hull_cinema_club
| apps
| hcc_core
| movie_importer
| phoenix_app
This works well enough on my dev machine, however I’m having a hard time deploying using edeliver and am wondering whether that it a sign that there is a more optimal way to structure that application.
I’m pretty new to Elixir so any feedback or advice on sharing schemas between projects would be greatly appreciated.
Thanks!
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Deploy Phoenix to your own VPS with PaaS ease: push-to-deploy, zero downtime, auto SSL, managed Postgres. 14-day free trial at potions.io
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
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #elixirconf-eu
- #metaprogramming
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
**Building the future of software with AI, trust, and human connection.**
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
kokolegorille
Looking at your structure, I guess You use mix new … --umbrella, then go to apps and build phoenix app.
But there is also another way of doing this
After, You build the movie_importer, You will get this structure
WIth hull_cinema_club acting as core. I tend to prefer this, as it simplify struct a little bit, as there is no need to build phoenix_app and hcc_core by hand. And also, the web part is configured only for web. While the core is the db part.
Also configuring tests is automatic, while in your case, You will need to make it by hand.
It’s just a matter of taste, I used the same structure as yours before…
rob_marsh
Thanks for the advice - I hadn’t thought to create the umbrella project using phoenix but I can definitely see how that makes things tidier. Also good to know that I’m not completely on the wrong track.
pedroassumpcao
Also, if you already have started the project as umbrella without the web piece, you can use
mix phx.new.webgenerator insideappsto create the web layer using Phoenix. The generator will identify the umbrella project and will remove everything you don’t need in the web app.