dewetblomerus
@victorbjorklund thanks for your @ThinkingElixir #167 on Phoenix Generators.
This would solve a problem at work where we want all new services to have certain observability libraries installed and to respond to a health check without logging, etc.
I tried your article Build your custom Phoenix phx.new generator
I can not get into a state where my modified generator and the original generator both work. I need this because it would be bad if someone goes to make a side-project on their work laptop and ends up with the company’s setup.
Here are the steps I took:
- Make a copy of the
installerdir with my own name. - Rename the file and module name for
/lib/mix/tasks/phx.new_project.ex - Edit
/templates/phx_single/mix.exs
Now I can run mix phx.new_dw foo and I get the modified mix.exs. But if I run mix phx.new foo I also get the modified mix.exs.
I tried renaming the app: :phx_new in the installer/mix.exs. This really made it seem like I found the correct thing, because it generated a differently named file in ~/.asdf/installs/elixir/1.15.4-otp-26/.mix/archives/ but still, both commands generate the modified code.
I tried deleting and re-generating the files in ~/.asdf/installs/elixir/1.15.4-otp-26/.mix/archives/, this produced the same result.
Do you have an example of a GitHub project where you have a modified version of the generator that still allows you to call the official Phoenix generator when you want to?
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Producing high quality Elixir screencasts since 2017.
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
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #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.
Bringing learning, work and compliance together since 1987.
**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 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
dimitarvp
Oh man, if you succeed in this and even open-source it, I am definitely buying you a pizza and a beer!
LostKobrakai
That renames just the archive, but the mix task names are still infered from the module names of those mix tasks.
dewetblomerus
This rings true. But when I have two different
installerdirectories, one with amix phx.newand the other with amix phx.new_dw, both of them ends up applying the changes I made in my newinstaller_dwdirectory.dewetblomerus
I will at least open source a toy version of this if I got it working. No pizza or beer required.
For personal projects, my only need is that
mix_test_watchis included on every Elixir project ever