Ciboulette
Hello,
I am currently building a Mix archive in Elixir. I have multiple library dependencies. here my mix.exs
defmodule Zenaton.Mixfile do
use Mix.Project
def version, do: "1.0.0"
def project do
[
app: :zenaton,
version: version(),
elixir: "~> 1.4",
build_embedded: Mix.env == :prod,
start_permanent: Mix.env == :prod,
name: "zenaton",
aliases: aliases(),
deps: deps()
]
end
# Configuration for the OTP application
#
# Type "mix help compile.app" for more information
def application do
# Specify extra applications you'll use from Erlang/Elixir
[
extra_applications: [:amqp, :porcelain, :logger, :cowboy, :plug, :httpoison, :dotenv],
mod: {Zenaton.Application, []}
]
end
defp deps do
[
{:amqp, "~> 0.3.0"},
{:cowboy, "~> 1.1"},
{:dotenv, "~> 2.0.0"},
{:httpoison, "~> 0.13.0"},
{:plug, "~> 1.4"},
{:poison, "~> 3.1"},
{:porcelain, "~> 2.0"},
{:uuid, "~> 1.1"}
]
end
defp aliases do
[
build: [ &build_releases/1]
]
end
defp build_releases(_) do
Mix.Tasks.Compile.run([])
Mix.Tasks.Archive.Build.run([])
Mix.Tasks.Archive.Build.run(["--output=zenaton.ez"])
archives = "./zenaton_archives"
File.rename("zenaton.ez", "#{archives}/zenaton.ez")
File.rename("zenaton-#{version()}.ez", "#{archives}/zenaton-#{version()}.ez")
end
end
I can install very easily this archive by doing: mix archive.install zenaton.ez and when I’m launching my task command with mix zenaton.listen. I have this error:slight_smile:
** (FunctionClauseError) no function clause matching in Mix.raise/1
(mix) lib/mix.ex:275: Mix.raise({:error, {:amqp, {‘no such file or directory’, ‘amqp.app’}}})
(mix) lib/mix/task.ex:294: Mix.Task.run_task/3
(mix) lib/mix/cli.ex:58: Mix.CLI.run_task/2
(elixir) lib/code.ex:370: Code.require_file/2
It seems that the archive is not built with amqp dependencies.
In my run/1 function in mix task, I added Application.ensure_all_started(:zenaton) to load the dependencies. But it doesn’t help
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Producing high quality Elixir screencasts since 2017.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 9- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
josevalim
The first question that comes to mind is why you want to have such an archive with dependencies. Archives should mostly be used for extending Mix with plugins and not much else.
Ciboulette
Ok, I would like to build a global mix task that is quite similar to
mix phoenix.server: it will launch a local HTTP server and a rabbitMQ connection, that’s why I’m using AMQP. Do you think it’s a problem ?jeremyjh
Why would that need to be global? Couldn’t it be added by a dependency in the consuming project?
phx.serveris not a global, it is defined inphoenix. The only global isphx.new.Ciboulette
Ok So I am going to sum up what I would like to do and you may have an idea to solve my problem:
I would like to create a global CLI that can be installed on every machine that has Elixir installed. This CLI will have a command that will start a local HTTP server and a rabbitMQ connection.
How will you proceed?
LostKobrakai
I’d build an escript, so you’d only need erlang on the machine executing the cli.
kylethebaker
Is this meant to be a tool used for development on other elixir projects? Then I would do what @jeremyjh said and put it in it’s own standalone project as a
Mix.Taskwith its own set of dependencies as needed. Then in the other projects you want to use it on you would just add it to your mix dependencies anddeps.get. As mentioned, this is howphx.serverandecto.createand stuff work: they come from the phoenix and ecto dependencies included in the project.If it’s meant to be a standalone tool that is used outside of the context of an existing Elixir project then I would do like @LostKobrakai and create an escript. Then you can put this escript into the
$PATHon the different machines and run it just like any other command line tool.If it’s meant to a full on application (as in not really just a tool) then you may want to consider using Distillery and creating a full release. That way it will come packaged with the erlang runtime and you’d deploy it like a production application.
ericmj
Archives do not include dependencies because archives are loaded into the same VM as Mix and the users application when they run their application through Mix. If archives were to include dependencies they would conflict with the user’s dependencies since you can only have one instance of an application loaded. So for example if the user depended on poison your archive would break them since you load poison yourself.
Archives should only be used when you need to interact with or extend Mix. If you just want to start an HTTP server it doesn’t sound like it would interact Mix so it should probably be an archive instead.
Crowdhailer
Should this end “it should probably be an escript instead”?
ericmj
Yes, thanks for the catch.