Skip to content
This repository has been archived by the owner on Sep 22, 2024. It is now read-only.

Make the plugins Erlang/Elixir applications #28

Open
mentels opened this issue Apr 3, 2017 · 4 comments
Open

Make the plugins Erlang/Elixir applications #28

mentels opened this issue Apr 3, 2017 · 4 comments

Comments

@mentels
Copy link

mentels commented Apr 3, 2017

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.

@michalslaski
Copy link
Member

*EPL.beam allows us to automatically configure cowboy routes and automatically register in the UI.

How do you suggest to address these?

@arkgil
Copy link
Contributor

arkgil commented Apr 3, 2017

Each plugin could configure its application environment (e.g. via env tuple in .app file), and point us to websocket handler.

@mentels
Copy link
Author

mentels commented Apr 3, 2017

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 .app file or .config files (mix.exs or config/*.exs files respectively for Elixir).

@arkgil
Copy link
Contributor

arkgil commented Apr 3, 2017

I think it's related to both #27 and #26 .

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants