KP123
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
First Post!
al2o3cr
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.
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









