Menkir

Menkir OP

Hi guys,
I’d like to talk about my attempt to build a plugin mechanism for LiveComponents. My goal is to build a WebApp that goes through a LiveView and consists of several LiveComponents.

The LiveComponents are rendered in dependence of live_actions. Since the routes for the live_actions are defined at runtime, the router has to be recompiled as soon as a new plugin is added or triggered. Currently I use a /plugin folder within the project. To save the compiled modules I use an ETS cache. The plugins implement a behaviour so that the system can be completely agnostic and only renders what corresponds to the behaviour.

The router looks like this:

  scope "/", TestWeb do
    pipe_through :browser

    live "/", TestLive, :index
    live "/error", TestLive, :error

    for plugin <- TestWeb.PluginController.get_actions() do
      live "/#{plugin}", TestLive, plugin
    end

    get "/recompile", PluginController, :recompile
  end

What is currently still a stumbling block is the source code in the /plugins folder. This should not be left lying around forever, but should be compiled once and then load the beam files as needed (restart).

How do you find this method? Since Elixir is a language that has to be compiled first, this approach seems very clumsy to me. Maybe it could be done better. Criticism and suggestions for improvement are welcome :slight_smile:

Where Next? Top

Trending in Questions Top

stjefim
Hello! Suppose you are building workflow (order / task / payment) processing system with the following requirements: Each workflow con...
New
jonnycharles
I’m in search of an Elixir library that offers PDF generation capabilities similar to Ruby’s Prawn. While there have been discussions abo...
New
spammy
I’m looking to build a personal workflow to quickly deploy web applications written in elixir/phoenix, for local consumption (ie not on t...
New
dli
Before I dive in myself, did anyone successfully sprinkle Hologram into their existing LiveView app? Looking for hints regarding: Addi...
New
bottlenecked
Hi all, I wanted to ask how the community is dealing with post-release steps. Today we have Ecto migrations, which make sure that the db...
New
roeland
Kia ora, We have been using elixir-google-api to connect to Google Drive. However, with the updates to Tesla due to CVEs this is now bro...
New
michallepicki
I am using Oban and occasionally, shortly after a deployment, a handful of jobs can fail because of dependency on other parts of the syst...
New

Other Trending Topics Top

JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Damirados
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge &amp; Solve. They are GUI (Emerge) and State management (S...
New
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
ausimian
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New
juhalehtonen
There has been a thread to discuss the Stack Overflow Developer Survey on this forum every year since 2018, so here’s yet another one for...
New

We're in Beta

About us Mission Statement