Elixir Deployment

Talk given at Elixir London meetup 2017.

1. DEPLOYING ELIXIR BY TETIANA DUSHENKIVSKA
3. HEROKU VS USING RELEASES
4. DEPLOYING USING RELEASES
5. PICK RELEASE MANAGER EXRM DISTILLERY REBAR3
7. WHERE SHOULD WE BUILD A RELEASE?
10. CREATING A RELEASE OF OTP APP WITH DISTILLERY
11. ADD DISTILLERY DEPS TO MIX.EXS {:distillery, "~> 1.0"}
12. FETCH DEPS $ mix deps.get
13. RELEASE IT! $ mix release ==> You are missing a release config file. Run the release.init task first
14. DO AS DISTILLERY TOLD YOU $ mix release.init
15. GENERATED REL/CONFIG.EXS
17. REL/CONFIG.EXS #/rel/config file content ... include_ertc: false #needs to have erlang installed. ... release :app_name do set version: current_version(:app_name) end
18. PRODUCE A RELEASE MIX_ENV=prod mix compile mix release --env=prod --verbose option for more info
19. YOU CAN FIND YOUR RELEASES AT _BUILD/PROD/REL/APP_NAME/RELEASES/0.0.1/
20. AND TARBALL IS PRODUCED! .TAR.GZ
21. AND YOU HAVE BUILT YOUR RELEASE!
23. ...BUT SOMETIMES THINGS GO WRONG
26. SOLUTION 1 SHORTEN LONG MODULE NAMES $ find . -type f -print| awk -F/ ' length($NF) > 99 '
27. SOLUTION 2 PRODUCE TARBAL MANUALLY MIX_ENV=prod mix compile mix release --env=prod --no-tar cd /my_app/_build/prod tar -cvzf my_app.tar.gz
28. GOT IT SORTED!
29. DEPLOYING
30. POSSIBILITY 1 MANUALLY COPY .TAR.GZ TO THE PROD SERVER # copy release to prod server $ scp -i _build/prod/rel/my_app/releases/0.0.1\ /my_app.tar.gz user_name@server_name:/home/my_app/releases/0.0. my_app.tar.gz
31. UNTAR IT # ssh to the server ssh user_name@server_name # untar your release on prod server tar -xzf ~/my_app.tar.gz
32. CHECK IT'S WORKING # start it on prod server my_app/bin/my_app console # you should see the logs # start it as a daemon on prod server my_app/bin/my_app start my_app/bin/my_app ping # > pong
33. A BIT OF AUTOMATION
35. GET TO KNOW YOUR SERVER
36. .TAR.GZ VS .DEB?
37. .DEB CONTAIN DEBIAN-BINARY CONTROL.TAR.GZ DATA.TAR.GZ
38. DEBIAN-BINARY 2.0/n
39. CONTROL.TAR.GZ ARCHIVED CONTROL FILE Package: my.app Version: 1.0.0 Architecture: amd64 Maintainer: Inflowmatix Priority: optional Description: Packaged on debian server
40. DATA.TAR.GZ THIS IS WHERE OUR APP BINARIES GO (FROM _BUILD DIR)
41. LET'S SEE THE EXAMPLE
43. CIRCLECI(2.0) BUILD RELEASE(NO TAR) cd my_app if [ "${CIRCLE_BRANCH}" == "master" ]; then MIX_ENV=prod mix compile mix release --env=prod --no-tar --verbose ...
44. PREPARE DATA.TAR.GZ ... cd /my_app chmod 755 _build/prod/rel/my_app/bin/my_app ... mkdir -p /my_app/package/ cd /my_app/_build/prod/ tar --xform="s%^%/home/my_app/%"\ -cvzf /my_app/package/data.tar.gz rel/
45. PREPARE DEBIAN-BINARY ... echo "2.0" >> package/debian-binary
46. PREPARE CONTROL.TAR.GZ ... mkdir -p package/control cd package/control printf "Package: ..." >> control; tar -zcf /my_app/package/control.tar.gz .
47. CREATE .DEB PACKAGE ... cd /my_app/ version=$(git describe | sed 's/v//'); mkdir releases ar -rc releases/my_app_$version.deb\ package/debian-binary package/control.tar.gz\ package/data.tar.gz rm -rf package/ fi
48. STORE .DEB IN ARTIFACTS(CIRCLECI) - type: artifacts-store path: /my_app/releases destination: releases
49. DOWNLOAD RELEASE SSH TO THE SERVER $dpkg my_app_0.0.1.deb $/home/my_app/bin/my_app start
50. SUMMARY LOT'S OF OPTIONS 3 PIECES NEEDED TO PRODUCE .DEB PACKAGE COULD BE FRUSTRATING, BUT DON'T GIVE UP! CHECK WHERE YOU ARE BUILDING A RELEASE