Which version of Distillery are you running? 1.5.* has issues on FreeBSD.
Thanks href,
From my mix.exs
{:distillery, "~> 1.4.1"}
mix.exs
represent the deps specs, and not the ones you actually got. Get the version by running mix deps
or looking in the mix.lock
file
Well, its specific enough in this case, since 1.5.x
is not in ~> 1.4.1
. ~> 1.4.1
is syntactic sugar for >= 1.4.0 and < 1.5.0
$ mix deps
* distillery 1.4.1 (Hex package) (mix)
locked at 1.4.1 (distillery) 546d851b
ok
ok then it should work with freebsd. Iām not using edeliver so Iām not sure I can help more. Sorry
@NobbZ true, I wasnāt caffeinated enough.
Iāve created a new project, and it builds, deploys, and starts, but once againā¦ I canāt see it via the reverse proxy or directly from the production server - same issue as I had with the earlier project I posted about after moving to Phoenix 1.3.
Is there a better alternative to distillery + edeliver?
I personally just git pull to the prod server, run my ./release.sh
script, which uses distillery to build a release (after getting deps, npm, building production assets, etcā¦ etcā¦) and then it injects it into the system causing a rolling upgrade of the production server (down for about ~3 seconds).