Learning resources about deploying Phoenix (no fly.io, no Docker)

What kind of resources?

Run mix release, open the release folder and find the binary to start your application. The code, runtime and configurations are all packed with the release.

What can I say, it worked the first time after just reading the official releases documentation (that you summarized nicely here).

I am quite impressed! This is great!

Thank you

Usually docker is used because that’s the simplest way to make sure the architecture between an external build machine and machines used to run the release are the same. If you can have the build machine match without using docker that works just as much.

I am building the release on the target directly (I use Ansible to automate).
It worked the first time with just a couple of env variables, that’s really amazing.

Yeah that works. Not a common solution though as you need build tooling on that server and you also have the load of doing the build there. Both things people tend to avoid in production.

Yeah yeah, that’s fair and stated in the docs

Just wanted to start from the basics and climb to state of the art.

This is my article about deploying to Ubuntu <= 20.04 LTS

What is the best way to deploy a Phoenix application to EC2 or Digital Ocean? - #5 by sanswork is how I used to do it though I use fly these days.

There’s https://staknine.com/deployment/ but the latest is 2022. He produced a book at Phoenix Deployment Handbook. There’s also Deploying Elixir with his companion at Deploying Elixir eBook. Both are great resources and I’ve seen some other tutorials for Digital Ocean or running Elixir processes with supervisord. There’s also a library that helps create the scripts for that like mix release but it’ll take me a while to find that in my sea of GitHub stars.

Hi Carlo. Ansible is the way I went in combination with droplets on Digital Ocean. I found some excellent articles on the Cogini blog when it was starting out like yourself trying to figure out an approach. It takes some work but if you are down for it the work can be pretty rewarding. I wrote my own scripts using the information on Coflgini as a reference. I did not want to use theirs as is because it felt like I would be putting someone else in charge of my Devops and I needed to know how everything works under the hood in case issues arise. Hopefully it helps.