mrkurt
How do you package your Phoenix application for deployment?
Hello! I run a cloud company, we want to build the best possible Phoenix deployment experience. The goal is a CLI based launch command that takes a Phoenix app directory, sets the right configuration secrets on our service (SECRET_KEY_BASE and DATABASE_URL, so far) and then builds + deploys the app as quickly as possible.
For Ruby and Rails, we just use the default Heroku builder. It works very well.
The available Phoenix buildpacks are very slow and incredibly brittle. We can’t really use those, we need a better option.
How do you all package your apps for deployment today? Specifically:
- Do you use mix release?
- Do you have a Dockerfile?
- Do you run a CI system, and which one?
Thank you for the help!
Most Liked
crova
1- Mix release
2- Nope
3- Only started using Sasa’s ci/cd library recently but nothing else.
vincer
Earthly is great although the caching story isn’t quite there yet, but it should get very very interesting soon. Here’s the Earthfile I use for all my projects these days: potionx/packages/templates/src/project/potionx/Earthfile at main · PotionApps/potionx · GitHub. You can also see the Pulumi code here and the Github Actions code here.
mrkurt
We made those work first thing! ![]()
Popular in Discussions
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









