How to run custom tasks in production by manually calling them?

Your second option (/bin/app eval …) looks right. Mix is a build tool and is not a part of your release. There’s a nice example of how this can be done in the Phoenix “Deploying with releases” docs.

For passing arguments, you should be able to just pass them as arguments to the command you’re running — the mix release docs have the example of bin/RELEASE_NAME eval "IO.puts(:hello)".

That doesn’t answer the question of “how to pass an argument to my custom function”

bin/RELEASE_NAME eval "IO.puts(:hello)"

because it passes some code to eval

For instance:

``

defmodule MyApp.Release do
  @app :my_app

  def abc(a1, b1, c1) do
    # [.......]
  end

How to pass a1, b1, c1 to abc() in

$ _build/prod/rel/my_app/bin/my_app eval "MyApp.Release.abc ???"

?

Just pass them? Eg

$ _build/prod/rel/my_app/bin/my_app eval "MyApp.Release.abc(1, \"str\", :atom)"

You’re basically calling a function the same way as you would in IEx, so you can pass any elixir data type.

Add-on to this which is not super clear from this section of the docs:

I was trying to forward command-line arguments directly to my Elixir code being run. Doing it the naive way doesn’t work for arbitrary unexpected numbers of arguments and other reasons:

$ _build/prod/rel/my_app/bin/my_app eval "MyApp.Release.abc(\"$1\", \"$2\")" # this doesn't even properly escape double quotes, and ways to do that within bash are not consistent across systems

There is a supported way to forward the command line arguments though:

$ _build/prod/rel/my_app/bin/my_app eval "MyApp.Release.abc" "$@"

The command line arguments can then be accessed in your Elixir code using System.argv(). Hope this helps anyone facing the same problem. This seems like a better solution to me for anything more complex than passing hard-coded values from the shell script.

If you’ve deployed your app using releases, it’s straightforward to fire up iex:

$ _build/prod/rel/my_app/bin/my_app remote
iex(1)> MyProject.Module.method(1, 2, 3)

Have you considered contributing the improvements to the official documentation?