I’m looking to deploy a Phoenix API to AWS. I don’t need any fancy features, I just need to be able to select a specific node type (high compute), and ideally it could be easy to deploy nodes. There are thousands of guides I’m finding, and the 3 i’ve tried were all broken. Is there a really good g…

Maybe GitHub - bitwalker/distillery-aws-example: An example application to go with the AWS guide in the Distillery documentation · GitHub for Deploying To AWS - Distillery Documentation

That guide is so broken that I just stopped following it. This is the one I’m doing now: https://cloud.google.com/community/tutorials/elixir-phoenix-on-kubernetes-google-container-engine It works great so far, the only part I’m confused on is where I define my environment variables so that REPLAC…

You can set REPLACE_OS_VARS in a pre configure hook. As for the distillery guide, it wasn’t broken at all when I followed it a few months ago.

Hmm weird. I encountered like 3 or 4 places that I fixed easily enough but it didn’t give me confidence in the guide. ultimately I stopped though because I didnt want to depend on amazon blackbox services which Ive had experience with before. Granted, my current method deals with Google blackbox ser…

Oh I see, its in the deploy scripts in _build/prod/rel/app/lib/ clever

You can set REPLACE_OS_VARS just before running the app. It’s being deprecated in favor of config providers, though. See Runtime Configuration - Distillery Documentation for more. Can you explain what you mean by pre-configure hook? Boot Hooks - Distillery Documentation …

Damn well this looks super confusing. I’ll have to get docker running start to finish first then ill figure out how to do that. How might I do that with this current strategy I’m doing, can you give me an examle of a single variable and where I put it so I don’t have to read all that (for now)

Let’s say you have something like config :app, db_path: "${DB_PATH}" in your config.exs somewhere. To make it replaceable at runtime, you’d need to set REPLACE_OS_VARS before starting the release. One way to do it is in a pre configure hook.

Oh I’m talking about doing away with this method “${DB_PATH}” and REPLACE_OS_VARS and just doing it the proper way with config providers im actually just reading now to see how to do it

You’d choose a config provider, copy it into the release, and that’s it, I think. Somewhere in rel/config.exs environment :prod do set config_providers: [ {Mix.Releases.Config.Providers.Elixir, ["${RELEASE_ROOT_DIR}/etc/config.exs"]} ] set overlays: [ {:copy, "rel/config/config.exs",…

Elixir Programming Language Forum

Best deployment guide for a Phoenix API to AWS?

Questions & Help Questions

9mm December 21, 2018, 6:55pm 13

Dude thank you. Alright I’ll try doing that next