dmitriid
Create a module in memory, refresh/reload on change
It’s one of those “if you try it, you can figure it out” questions. I’m just hoping someone has already done this before and has some quick tips or a link to look at 
The meat of the question is: I have something in a file (data, or a custom DSL, or anything, really). Using this something, I want to create and compile an Elixir module and load it into the running application. When that something changes (let’s say, a file watcher tells me that contents have changed), I want to re-create/re-compile that module and reload it.
I know that I should start looking at Module.create/3. Perhaps there are other things I can/should look at and consider?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Error tracking, logs, APM, uptime and cron monitoring in one dev-friendly platform. Find and fix problems before your users notice.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #performance
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Develop your skills with books, videos, and courses.
Bringing learning, work and compliance together since 1987.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
First 5 of 5 Posts
kokolegorille
You might use @external_resource attribute on a module…
If the external resource file change, the module will recompile.
03juan
You could try Code.eval_string/3 if you want to parse the changed “something” file from within Elixir to produce a string representation of the module def.
Alternatively Code.eval_file/2 if you dynamically write/update an
.exfile from your “something” file.mudasobwa
This is compilation-time dependency, which helps to mark a module as “recompilation needed” for the regular elixir compiler when say
mix compileis to be invoked next time. It has zero value here, unfortunately.Yes, kinda. There is a pitfall one should be aware of: the module recompilation is not instant.
I would spawn the process as gateway access to the module to be recompiled that both recompiles whatever is needed and its mailbox acts as a queue for both subsequent recompilations and all the interactions with this module. That way one can be sure that the module gets accessed if and only it’s available.
Please note, that
Module.create/3accepts an AST. If you want to load a regular.ex[s]file, useCode.eval_file/2as suggested by @03juan.kokolegorille
Oops, my bad… I did not catch it should be for runtime.
dmitriid
Good point/catch about the queue. Especially if I want this to be based on a custom DSL or custom data, compilation will definitely not be instant.