Sebb
Are pool specific docker containers possible with Flame?
FLAME nodes effectively clone and start your entire application.
from: FLAME — flame v0.5.3
I’m considering flame for a project where I need workers that pull in a big dependency.
I don’t need it at all on the webserver. So I’d ideally build a container for the server and one for the pool. Is that possible (planned?).
Marked As Solved
LostKobrakai
No, not separate ones – one image running in all contexts. Let the app decide to not use BigDep outside of flame runners. I’d try that approach first and split stuff up only if it actually turns out to cause problems. Having a homogenous cluster is generally simpler than a heterogenous one.
But I’ve also just seen that the FLAME fly backend seems to support an :app config, which seems to be the way to let it start a different application for flame nodes to the one starting them: FLAME.FlyBackend — flame v0.5.3
Last Post!
Sebb
Popular in Questions
Other popular topics
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
- #websockets
- #supervisor
- #elixirconf-us
- #advent-of-code
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #hex
- #security










