Help debugging edeliver Phoenix site not showing

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 :slight_smile:

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

1 Like

$ mix deps

* distillery 1.4.1 (Hex package) (mix)
  locked at 1.4.1 (distillery) 546d851b
  ok
1 Like

ok then it should work with freebsd. Iā€™m not using edeliver so Iā€™m not sure I can help more. Sorry :slight_smile:

@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).