The Plug.init/1 method gets called during the compile step and not during the startup like I thought, is there someway to update a plugs config when the router supervisor tree is being setup? Background info: All of our applications/servers/api:s connect to a configuration server during startup and…

You can add a separate plug in the beginning of your “plug pipeline” to assign the necessary values into :private or :assigns fields, which can then be accessed by other plugs down the line. This separate plug would act like the init callback in a genserver.

That would still make a config request for each incoming web request, right? Besides, I would prefer to not have a dependency between the different plugs. If we add plug that requires some config information we would have to add that config key to the “Setup configuration” plug.

That would still make a config request for each incoming web request, right? I would imagine that you would request the config at the start up of your web app, and save it into either a module with :code.load_binary/3 (if the config won’t change for the life time of the app) or into a genserver (…

That was what I was afraid of. I think we will just add a backing genserver for each plug. If the plugs behaved like genservers then we would not have had this problem but perhaps the the current plug behaviour gives you some other benefits.

Plugs are functions, basically … so they can’t really behave like genservers. Why would you add a genserver for each plug though? Wouldn’t one be enough? It would be a bit more efficient (less message passing between processes, the webserver’s and your genservers’). But I would probably go with th…

Why would you add a genserver for each plug though? Wouldn’t one be enough? Each api can have different plugs enabled so we can’t have a large genserver that loads the configuration for every one of them. For example, we have these two plugs which both need access to configuration values that we…

See this post: [image] Session cookie domain option Questions And another one from @chrismccord himself: you could make a plug that calls the Plug.Session init, at runtime plug MySession, ... defmodule MySession do def init(opts), do: Plug.Sesson.init(opts…

tnx @LostKobrakai , so I guess it’s not possible to configure a plug at runtime, the solution seems to configure the call to a plug (every time) instead of just once on init.

I’m not sure what you expect. You either have compile time configuration (init/1) or runtime (call/2). “Once on init” is just a variation of “retrieve it every time” in that the caller queries the config from any kind of runtime cache like e.g. the app environment or some started processes instead o…

Elixir Programming Language Forum

Configuring Plugs during runtime

Questions & Help Questions

i-n-g-m-a-r August 12, 2018, 12:54pm 8

@Gyllsdorff did you find a solution to configuring plugs at runtime?