Best practice for self hosted Phoenix distributions

I’m intrigued by the new Campfire offering by Once. If I wanted to distribute a Phoenix application for an end user to self host how would I go about that? Are there guides or documentation? My main concerns are around the one line deployment and automatic updates. I know I can build releases with Dockerfiles but how to build releases fingerprinted for specific users for example. Also I can’t expect end users to manage a/b deployments or load balancers so updating needs to be handled in an automated fashion by me as well. Could be a good use case for hot code reloading.

Any guidance is welcome. Thanks

I don’t quite follow this part - somebody needs to know how to maintain & troubleshoot those things on an ongoing basis. My interpretation of the Once offering is that that’s the end-user’s problem.

The linked web page said:

Each Campfire installation pings our server once a day to see if there are any updates. If so, it’ll download and automatically install them.

So, there are automatic updates. I don’t think it is zero down-time though.

But it could be zero downtime because of the BEAM? Or is that only for when I control the deployment infrastructure as well?