Starting the worker without mix - as on distillery releases

[kleber-gueriero]

As in a release with Distillery there would be no mix to execute the faktory task, follow the explanation about Starting the Worker in the Readme, using the mix task wouldn't be possible.

Maybe it's just a case where I'm missing some basic knowledge and for others it'd be more obvious, but I think that maybe it would be nice to have in this section how one would start the worker in an environment without mix.

[cjbottaro]

Arrgg, my Github notifications are broken. Sorry for just now seeing this.

@acj I seem to remember you either did some work regarding this or have some knowledge on the subject?

I do all my deployments with Kubernetes or some kind of container orchestration, so it's super easy for me to just deploy containers that have mix; I have zero experience with standalone Elixir/Erlang releases.

I'm all for working with standalone releases, I just don't really know how or where to start. I'll look into it, but any help would be greatly appreciated.

[acj]

+1 to having standalone instructions -- preparing them will help to suss out any hidden dependencies on mix. I don't have any spare cycles at the moment, unfortunately, but it shouldn't be too hard to build a Distillery config for this app because its lifecycle is so simple. There's a good walkthrough in the docs.

I'd be happy to review/test a solution if someone has time to work on this.

[cjbottaro]

This will finally be done in 0.9.0 using Elixir 1.9.0's "mix release" feature.

[kleber-gueriero]

Wow...There are answers here since Nov, 2018 and I didn't notice...what a shame on me.
Thank you very much for help and clarification.