arathunku
How to match route when hostname is not known at compile time and simply matching by . is not possible?
I hope nobody will mind me resurrecting old thread instead of creating another one for very similar problem.
Does anyone have any working example where the hostname is not known at compile time and simply matching by . is not possible? Example: dynamic ad-hoc PR envs with some hash in the domain name. myapp-{{random string}}.example.comI found a workaround with replacing “host” on conn and it matched the route, but LiveView fails match in phoenix_live_view/lib/phoenix_live_view/route.ex at main · phoenixframework/phoenix_live_view · GitHub and keeps reconnecting.
Most Liked
sodapopcan
(I forgot where I originally got this code from, I know it was on this forum somewhere)
hauleth
You will need to write Plug that runs before your router and that translates from domain to path route.
LostKobrakai
The socket definition is not a plug though. All it does runs before the endpoint enters it’s own plug pipeline. Feel free to take a look at more detail here:
Popular in Questions
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









