woohaaha
Why does BeaconCMS need to be in an umbrella app? Could it have been done another way?
I’m really interested in the BeaconCMS project but it requires using an umbrella app. I’ve used an umbrella fairly recently and found it a little too cumbersome. I much prefer the Phoenix mono app happy path ![]()
I was wondering if anyone knew why BeaconCMS was built as an umbrella? What is the reasoning for making that decision? What benefits do we gain?
There are some other elixir based CMS’ that aren’t umbrellas so I’m wondering what’s the difference?
I did try to setup BeaconCMS earlier but the need to customize the umbrella along with thinking about deploying an umbrella stopped me after +20 min of customization. I also have not used any other elixir cms so if anyone has some thoughts I’d greatly appreciate it.
Thank you
Most Liked
TheFirstAvenger
Beacon CMS does not require an Umbrella. For a non-umbrella, I believe the only two differences in the walkthrough are 1) adding dependencies happens in one mix.exs instead of two and 2) you don’t have to cd before the mix ecto.reset call. Neither of these steps are Beacon specific.
Popular in Discussions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance









