Umbrella App routing with Plug.Router app & Phoenix app

Your phoenix app is working if you visit one of its routes bypassing the plug app?

Correct. The apps are on different ports (4000 & 4004) so I can access the routes by their corresponding port, but I’d like to go to one port (for the plug app) and be able to access the routes in the Phoenix app.

I think the problem is that the phoenix router is not a plug, whereas forward is expecting a plug, I think you need to give it the endpoint and not the router?

Ah, thanks @amnu3387! As you suggested, forward "/chemistry", to: ChemistryWeb.Endpoint works. However, it doesn’t load the assets, and submitting forms fails because they’re missing the chemistry/ prefix. Might have to figure out a different routing solution.

Thanks for your help!

Forward will eat the prefix, I think you want something more in line with what is being done here in this sample app

https://github.com/wojtekmach/acme_bank/blob/master/apps/master_proxy/lib/master_proxy/plug.ex

So one plug above where you pretty much raw match on the path, followed by a call to the appropriate phoenix endpoint or plug (in your case). Not sure this solves the assets, but at least the path will be passed entirely

The phoenix router is most definitely a Plug You can forward to a router as much as you like so that’s not an issue.

Ah - I just skimmed through the Router src and didn’t see the init method?
So what’s missing there? The app being a dependency on the other umbrella app?

We use a very similar setup, here’s how we structured the app:

The plug app defines a router that uses match <path>, to: <plug> to forward requests without altering the path.

  match "/events/*_", to: Events.Router
  match "/exq/*_",    to: Exq.Router
  match "/health",    to: Health.Router
  match "/report/*_", to: Report.Router
  match "/stats/*_",  to: Stats.Router

Then each of the umbrella apps defines a Router module, with Phoenix.Router for the nice url helpers.

We add a TestEndpoint module in each umbrella app under /test/support/test_endpoint.ex and load it conditionally in the Application module based on Mix.env

  def start(_type, _args) do
    children = case Mix.env do
      :test -> [Health.TestEndpoint]
      _ -> []
    end
    Supervisor.start_link(children, strategy: :one_for_one, name: Health.Supervisor)
  end

This allows you to develop each umbrella app in isolation, then stitch them all together with the plug router.

The plug router has to depend on every other app to forward to them:

 defp deps do
    [
      {:events, in_umbrella: true},
      {:health, in_umbrella: true},
      {:stats, in_umbrella: true},
      {:reports, in_umbrella: true},
   ]
  end

Have been trying to forward the routes and no success. Then I found this thread, I am trying to use the match function but seem like it crash with the Phoenix.Router’s match/5 function .

Can someone provide an example how to use the Plug.Router and the match function?

I am new to Elixir/Phoenix,

Plug.Router — Plug v1.20.2 has an example for using Plug.Router.
It’s different to the Phoenix.Router that would be generated with a new Phoenix app.

I think you could achieve the same effect with a Phoenix.Router using :* as the verb and a glob path:

match(:*, "/some/prefix/*path", SomeOther.Router, nil)