bluejack
Building out an API server to handle json query/response. Setting up the environment I select all the recommended flags for building an API only server.
mix phx.new myjsonapp-api --no-html --no-mailer \
--no-gettext --binary-id --app moondream_api --no-assets
When running it I get a boatload of errors pertaining to to the lack of an available live reload socket.
Researching, I see that the --no-html is incompatible with live reload, which is a bit of a bummer, but I get it.
So, I set code_reloader to false in the dev.exs endpoint configuration, but that didn’t stop the errors.
So, I for further good measure I commented out the code in the endpoint itself, as well as the LiveDashboard configuration.
None of these things seem to stop the attempt of some part of the framework to keep making calls to GET /phoenix/live_reload/socket/websocket
Question 1 – is it actually confirmed true that you can’t do live reload on a json api server?
Question 2 – what am I missing by way of turning off this very nice development feature?
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix 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
- #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.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
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.
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
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 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
LostKobrakai
So first of all you should differenciate between phoenix live reload and phoenix code reloader.
Phoenix live reload makes a website reload when any of the files you have a pattern for changed. That’s a JS feature and hence only works with html pages. A json response in a browser cannot execute JS and therefore the server cannot tell the JS client to reload the current page. This is even a separate package, because it only makes sense in a limited context.
Phoenix code reloader is a different feature. It doesn’t cause http requests being made, but if there happens to be an http request it makes sure to recompile any changed files, so the response is built using latest changes in source files and not using stale logic. That plug is part of the phoenix library and therefore generally available if you use phoenix. That one is useful to developing any webserver functionality no matter if html or any other content types are served.
bluejack
Thanks for that clarification; I did not understand the distinction.
And furthermore, I have ascertained that the answer is that I am running my api server on the same port that I was previously running my webserver on, and an open tab to my localhost was polling home for updates… to my api server, which rightfully didn’t know what it was talking about!
Whee!