You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 22, 2024. It is now read-only.
Are there any advantages by treating *EPL.beam files as plugins over making plugins valid Elixir/Erlang applications? The web socket handlers could be configured via the config file.
The text was updated successfully, but these errors were encountered:
Have a look at erl_cowboy and how it's being used in dobby_rest. If I understand the problem correctly, you could have tuples like {"/path/to/my_resource", handle_module} passed to the Erl/Ex application env either through the .app file or .config files (mix.exs or config/*.exs files respectively for Elixir).
Are there any advantages by treating
*EPL.beam
files as plugins over making plugins valid Elixir/Erlang applications? The web socket handlers could be configured via the config file.The text was updated successfully, but these errors were encountered: