-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make the plugins Erlang/Elixir applications #28
Comments
*EPL.beam allows us to automatically configure cowboy routes and automatically register in the UI. How do you suggest to address these? |
Each plugin could configure its application environment (e.g. via |
Exactly, that was my idea. 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 |
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: