Context
We are trying to use edeliver to deploy a "Hot Upgrade" of a Phoenix Web Application to a remote Virtual Machine instance.
Our aim is to build an "upgrade" version of the app each time so that the app can be "hot" upgraded in production…
I've Phoenix app (I created it with --api flag) that has some additional data required to process requests that I store in priv/data/filters.csv.
So it works fine in dev mode, I can read this file like: File.stream!("priv/data/filters.csv"), but…
I get this error when I run mix edeliver build release production --verbose
A remote command failed on:
deploy@80.111.111.80
But when I log into the server, Elixir (and thus Mix) seem to be installed fine.
ssh…
I'm working through a couple of different How-Tos (the main in the project plus several via Google search) for edeliver to deploy code but I can't find a solution to this Could not invoke task "distillery.release": 1 error found! problem:
$ mix…
The CodeReloader (in dev mode) is using Mix.Config. This fails when using distillery releases in dev_mode because mix is not available in releases.
Is it possible to completely disable CodeReloader in a Phoenix app, such that my app will not fail to…
Background
I'm trying to setup clustering between a few elixir nodes. My understanding is that I can set this up by modifying the release vm.args. I'm using Distillery to build releases and am following the documentation here:…
So basically I need some Ecto repository information (call it "Sample.Repo") to start the repo in a release task for Ecto 3. It's configured in a runtime config with a custom json config provider as described in…
Background
I'm trying to setup clustering between a few elixir nodes. My understanding is that I can set this up by modifying the release vm.args. I'm using Distillery to build releases and am following the documentation here:…
My application, when trying to run a release, has this fatal issue:
** (MatchError) no match of right hand side value: {:error, {:inets, {'no such file or directory', 'inets.app'}}}
It works fine when running it with mix on my localhost, however…
I used the following library to generate a soap Client out of my wsdl-Files.
https://github.com/bet365/soap
All works fine in my dev environment - i can successfully call the services.
The Problem:
When I build my Elixir Release by Distillery it…
Background
Using distillery to start an OTP App, I noticed that all the logs go to the ./var/log/ folder to 2 different files:
erlang.log.1
run_erl.log
Problems
I have issues here:
I don’t know what run_erl.log is supposed to log
I would like to…
Distillery version 2.0
Elixir 1.7.1
OTP 21.0
First, do a normal release and deploy with mix release. It created a build in prod/rel/app_name/releases/1.0.1-08f6b0c
Application working
now change something and again create a release with mix…
I have created the build using command MIX_ENV=prod mix release --env=prod --verbose. It successfully creates the build and I can able to run the console and ping commands and give me the pid. Even when I run the start command it successfully…
I have an elixir application with 3 umbrella projects. I am trying to automate their releases via distellary and edeliver.
I am able to create a release by running this command:
mix release --verbose --env="production" --name="se_example"
However…
In my umbrella project using distillery for releases, I have a db app config with the following:
config :main, Main.Repo,
adapter: Ecto.Adapters.Postgres,
username: "${DB_USERNAME}",
password: "${DB_PASSWORD}",
database: "${DB_NAME}",
…