JoeZMar
What is the recommended way to deploy right now? And what is everyone’s thoughts about Docker?
I have been a long-time user of Gigalixir, but want to move to a DigitalOcean instance. I’ve always had my eye on running on a Ubuntu droplet and having more use of OTP having it run directly on the server.
I’ve always been slightly interested in Docker, but I heard that you lose the ability to run mix commands and a few other things. I just got back from EMPEX LA and someone was telling me how this isn’t true and that running within a Docker instance you have more efficient memory usage.
I also hear about eDeliver a lot less. Is mixing Distillery and eDeliver not a thing anymore? I’ve also heard of building the image with Docker and then running it on a DO instance.
Deployment has always been shaky for me and when I started using Gigalixir it was too easy to just stick with it, but I want to learn more about deploying without services like Heroku and Gigalixir.
What is the recommended way to deploy right now? And what is everyone’s thoughts about Docker?
Most Liked
danschultzer
I don’t think there’s any recommended way, but I wish there was some plug n play solution for people who just starts out with elixir.
We’ve been using ansible to manage builds with distillery and a docker container. It has been a very solid solution so far.
Github: GitHub - danschultzer/ansible-phoenix-build: Sample app with full build and deploy setup of a Phoenix app using ansible · GitHub
Blog post: https://dreamconception.com/tech/phoenix-automated-build-and-deploy-made-simple/
The inspiration came from this blog post by Piotr Włodarek.
Edit: We’re using DigitalOcean, and don’t run the apps inside docker containers.
danschultzer
There’s been quite a bit of interest for the guide and repo so I’ve updated them with Elixir 1.8, Phoenix 1.4, Ecto 3.0, ansible 2.6 and distillery 2.0.
gregvaughn
My company uses distillery and edeliver on AWS and hot deployments. Works fine.
I find Docker to bring philosophical friction to the BEAM culture. Docker comes from the culture of “servers as livestock, not pets” but BEAM comes from a culture of stateful long-running servers. I hear that people can have success treating BEAM like livestock in a container, but I don’t find that it solves any problems the BEAM faces. It’s a solution to different organizational-level concerns.
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
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance









