Deploying a Phoenix App with Podman and systemd

Hi all, the time has finally come to bring back the blog :slight_smile:

I recently got sick of building Erlang from source and switched to building and running containers with Podman and systemd, so I thought I’d write a minimal guide on how to deploy that way. The Phoenix guides are pretty focused on PaaS so I hope this can serve as a helpful alternative!

14 Likes

Nice post. Very thorough, and covers everything I was expecting.

Totally agree with you on the Quadlet naming convention. They’re just systemd unit files?! I hadn’t touched those, but I thought they were a whole other thing.

How did you come up with the name “corporate.fm” for your website?

1 Like

Well, technically I think they are somehow compiled into actual systemd units. Podman introduces additional syntax (e.g. [Container] and so on). I have no deep understanding of the mechanism by which this happens, but my experience learning about containers thus far tells me that if I did understand it I would probably be horrified. Maybe ignorance is bliss.

The abstraction does leak a bit, though.

It’s a reference to the megacorporation in Deltron 3030 :slight_smile:

2 Likes

Update: I could not resist acquiring the forbidden knowledge and now I can feel the bliss melting away