# Unable to deploy non-Phoenix Elixir app

**URL:** <https://community.fly.io/t/unable-to-deploy-non-phoenix-elixir-app/2164>\
**Category:** Questions / Help\
**Tags:** elixir\
**Created:** [August 11, 2021, 1:11pm UTC](https://community.fly.io/t/unable-to-deploy-non-phoenix-elixir-app/2164 "2021-08-11T13:11:25Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![jerome](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/jerome/32/17_2.png) [@jerome](https://community.fly.io/u/jerome)\
**Post date:** [August 11, 2021, 1:50pm UTC](https://community.fly.io/t/unable-to-deploy-non-phoenix-elixir-app/2164/8 "2021-08-11T13:50:19Z")

</div>

Oh sorry, I just looked at your `fly.toml` and I don’t think it’s doing what you think it should 🙂

`deploy.release_command` is a command that runs _before_ actually deploying your new app version. These are meant to be short-lived. Usually migrations.

I assume you explicitly set a command there because your Dockerfile has a different one?

You can do:

```auto
[experimental]
cmd = ["/app/bin/app_name", "start"]

```

---

_[View the full topic](https://community.fly.io/t/unable-to-deploy-non-phoenix-elixir-app/2164)._