Elixir Releases: How to release your app

In my slides I show different approaches how to release Elixir applications. Is it good to start application like we do it on our local machine? What is release? How can we create it manually with OTP? How can we configure them and create additional tasks before application start? I will try to give answers to all these questions and show you that it is not so difficult how you may think.

Transcript

1. HELLO
2. Elixir Releases
3. Problem
5. $ mix run !--no-halt
6. $ mix run !--no-halt Works out of the box Install Erlang Install Elixir Install mix Install hex mix deps.get …
7. $ elixir -pa "_build/prod/consolidated/" -S mix run —no-halt
10. When you have written one or more applications, you might want to create a complete system with these applications and a subset of the Erlang/OTP applications.
11. This is called a release.
12. Release An Erlang release is defined as a standalone node consisting of: 1. A set of OTP applications written or reused as part of the project, typically containing the system’s business logic. The applications can be proprietary, open source, or a combination thereof. 2. The OTP applications from the standard distribution that the aforementioned applications depend on. 3. A set of configuration and boot files, together with a start script. 4. The Erlang runtime system, including a copy of the virtual machine. Excerpt From: Francesco Cesarini Steve Vinoski. “Designing for Scalability with Erlang/OTP”.
14. $ mix new wut !--sup
15. wut.ex
16. application.ex
17. $ iex -S mix Erlang/OTP 21 [erts-10.1] iex> Hello world!
18. Create a release file
19. *.rel
20. wut.rel
21. {}.
22. {release, {"wut","0.1.0"}, {erts, "10.1"}, [{kernel, "6.1"}, {stdlib, "3.6"}, {sasl, "3.2.1"}, {elixir, "1.7.3"}, {compiler, “7.2.5"}, {logger, “1.7.3”}, {wut, "0.1.0"}]}. wut.rel
23. {release, {"wut","0.1.0"}, {erts, "10.1"}, [{kernel, "6.1"}, {stdlib, "3.6"}, {sasl, "3.2.1"}, {elixir, "1.7.3"}, {compiler, “7.2.5"}, {logger, “1.7.3”}, {wut, "0.1.0"}]}. wut.rel
24. {release, {"wut","0.1.0"}, {erts, "10.1"}, [{kernel, "6.1"}, {stdlib, "3.6"}, {sasl, "3.2.1"}, {elixir, "1.7.3"}, {compiler, “7.2.5"}, {logger, “1.7.3”}, {wut, "0.1.0"}]}. wut.rel
25. {release, {"wut","0.1.0"}, {erts, "10.1"}, [{kernel, "6.1"}, {stdlib, "3.6"}, {sasl, "3.2.1"}, {elixir, "1.7.3"}, {compiler, “7.2.5"}, {logger, “1.7.3”}, {wut, "0.1.0"}]}. wut.rel
26. Release An Erlang release is defined as a standalone node consisting of: 1. A set of OTP applications written or reused as part of the project, typically containing the system’s business logic. The applications can be proprietary, open source, or a combination thereof. 2. The OTP applications from the standard distribution that the aforementioned applications depend on. 3. A set of configuration and boot files, together with a start script. 4. The Erlang runtime system, including a copy of the virtual machine. Excerpt From: Francesco Cesarini Steve Vinoski. “Designing for Scalability with Erlang/OTP”.
27. {release, {"wut","0.1.0"}, {erts, "10.1"}, [{kernel, "6.1"}, {stdlib, "3.6"}, {sasl, "3.2.1"}, {elixir, "1.7.3"}, {compiler, “7.2.5"}, {logger, “1.7.3”}, {wut, "0.1.0"}]}. wut.rel
28. {release, {"wut","0.1.0"}, {erts, "10.1"}, [{kernel, "6.1"}, {stdlib, "3.6"}, {sasl, "3.2.1"}, {elixir, "1.7.3"}, {compiler, “7.2.5"}, {logger, “1.7.3”}, {wut, "0.1.0"}]}. wut.rel
29. {release, {"wut","0.1.0"}, {erts, "10.1"}, [{kernel, "6.1"}, {stdlib, "3.6"}, {sasl, "3.2.1"}, {elixir, "1.7.3"}, {compiler, “7.2.5"}, {logger, “1.7.3”}, {wut, "0.1.0"}]}. wut.rel
30. {release, {"wut","0.1.0"}, {erts, "10.1"}, [{kernel, "6.1"}, {stdlib, "3.6"}, {sasl, "3.2.1"}, {elixir, "1.7.3"}, {compiler, “7.2.5"}, {logger, “1.7.3”}, {wut, "0.1.0"}]}. wut.rel
31. {release, {"wut","0.1.0"}, {erts, "10.1"}, [{kernel, "6.1"}, {stdlib, "3.6"}, {sasl, "3.2.1"}, {elixir, "1.7.3"}, {compiler, "7.2.5"}, {wut, "0.1.0"}]}. wut.rel
32. mix.exs
33. {release, {"wut","0.1.0"}, {erts, "10.1"}, [{kernel, "6.1"}, {stdlib, "3.6"}, {sasl, "3.2.1"}, {elixir, "1.7.3"}, {compiler, "7.2.5"}, {wut, "0.1.0"}]}. wut.rel
34. $ iex -S mix
35. iex> :systools.make_script(‘wut’, [:local]) :ok
36. wut.boot wut.script
37. wut.boot ( )
38. wut.script $ cat wut.script | wc -l 500
39. $ erl -boot wut Erlang/OTP 21 [erts-10.1] Eshell V10.1 (abort with ^G) 1> Hello world!
40. iex> :systools.make_tar( !!...> ‘wut’, !!...> [{:erts, :code.root_dir()}] !!...> ) :ok
41. iex> :systools.make_tar(‘wut’) :ok
42. wut.tar.gz
49. $ erl -boot ./releases/0.1.0/start -env ERL_LIBS ./lib Erlang/OTP 21 [erts-10.1] Eshell V10.1 (abort with ^G) 1> Hello world! ☺
50. Is it enough?
52. Configs Start scripts
54. Distillery ~ relx for Erlang
56. mix.exs
57. $ mix deps.get
58. $ mix release.init
59. rel/config.exs rel/vm.args
60. rel/config.exs
61. rel/vm.args
62. $ MIX_ENV=prod mix release !--env=prod
63. $ MIX_ENV=prod mix release !--env=prod
64. $ MIX_ENV=prod mix release "--env=prod
65. _build/prod/rel/wut/releases/0.1.0/wut.tar.gz
67. $ bin/wut foreground Hello world!
68. Configs?
69. ENVs at runtime
70. lib/wut.ex
71. config/config.exs
72. $ MIX_ENV=prod mix release !--env=prod
73. $ REPLACE_OS_VARS=true MY_ENV=“Hi” bin/wut foreground Hi
74. $ MY_ENV=“Hi” bin/wut foreground ${MY_ENV}
75. Easy to setup Only strings {:system, var_name} vm.args ENVs at runtime
76. Config providers
78. Mix.Releases.Config.Providers.Elixir
79. config/config.exs
80. rel/config.exs
81. rel/config.exs
83. releases/0.1.0/sys.config
84. $ MY_ENV=“Hi” bin/wut foreground Hi ,
85. Is it enough?
86. For simple apps Yes
87. Ecto migrations
89. lib/release_tasks.ex
90. rel/commands/migrate.sh
91. rel/config.exs
92. $ bin/wut migrate
93. Conclusion
94. Powerful Handy Compile time/Runtime Standalone Conclusion