silverdr
Options for Building Erlang/OTP for a Phoenix application
When building Erlang/OTP (using asdf/kerl) for production server serving a (presumably typical setup of a) Phoenix application, what KERL_CONFIGURE_OPTIONS would you suggest to use from the list of available ones?
Application is a typical web application with PostgreSQL as data source.
I’d take --without-wx --without-javac are rather safe in such case? Anything else can be skipped?
Most Liked
LostKobrakai
The release does trim down the „runtime“ already. Only erts and otp applications your project depends on will be added. No need to optimize your kerl options.
Last Post!
silverdr
Do you mean there are no differences between Erlang/OTP compiled with everything enabled but then “trimmed” down by releases and one compiled with minimal set of options required for the phx application in question? While that in itself would be great,
- I saw final image sizes differ when using different build options. Need to double-check if I am not imagining things now but am like 90%+ sure
- The build/install time reduction may also be worth a bit of trouble. True that doesn’t have to be done every time, but still
Popular in Questions
Other popular topics
Latest Phoenix Threads
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









