axelclark
I’m playing around with my GrovePi and I’m looking to add or update some of the example projects in the Elixir grovepi library.
Some of the current projects don’t use Nerves and are made to run from Raspbian, for example the demo project for PivotPi. I was wondering if this is a better approach.
Should I always build the business logic of my projects outside of the Nerves application as a poncho project?
For a description of Poncho Projects, see
https://embedded-elixir.com/post/2017-05-19-poncho-projects/
In the past, e.g. my All of the Lights project, I’ve kept the hardware related business logic in the Nerves firmware app and brought in my Phoenix app as a poncho project.
Can you also bring in the your hardware business logic as a poncho project and just use the Nerves app to burn and manage the firmware? What are the pros/cons of that approach?
Where Next?
Trending in Questions
Other Trending Topics
Latest Nerves Threads
Latest on Elixir Forum
Sponsor Spotlight
Bringing learning, work and compliance together since 1987.
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
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #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.
Catch errors, track performance, monitor hosts and more.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
Producing high quality Elixir screencasts since 2017.
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 1- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
ConnorRigby
I can’t say when to use a “poncho” style project, but i can say at a certain point of complexity, you will know you need it. I don’t usually bother with small scale projects as i find it to be intrusive and cumbersome to flip flop between. But i will say that starting with the multi-app setup is much easier than splitting an existing large app up. I’m in the process of splitting a large, mature app up into a ponch application right now. I started it in April and am nearing completion now.
https://github.com/FarmBot/farmbot_os/compare/next?expand=1
743 files changed, in 213 commits has been a big commitment. I’d say if you think your project is going to be mature and maintained by someone other than you one day, start with Poncho