dinasol
how would I create database on release task with elixir 1.9?
I found on hexdocx Deploying with Releases — Phoenix v1.8.8 how to run migration, but not database creation
before I upgraded to 1.9 I had in my release script create and migrate following this: https://ronantreacy.com/blog/deploying-phoenix-applications-using-docker-and-distillery
here is my code for creating database:
defmodule Release.Tasks do
@start_apps [ :postgrex, :ecto ]
@myapps [:my_app]
@repos [MyApp.Repo]
def createdb do
# Ensure all apps have started
Enum.each(@myapps, fn(x) ->
:ok = Application.load(x)
end)
# Start postgrex and ecto
Enum.each(@start_apps, fn(x) ->
{:ok, _} = Application.ensure_all_started(x)
end)
# Create the database if it doesn't exist
Enum.each(@repos, &ensure_repo_created/1)
:init.stop()
end
defp ensure_repo_created(repo) do
case repo.__adapter__.storage_up(repo.config) do
:ok -> :ok
{:error, :already_up} -> :ok
{:error, term} -> {:error, term}
end
end
end
and then I ran it on the pre_start hook like this:
bin/my_app command Elixir.Release.Tasks createdb,
which worked well,
now when I am using 1.9 release, i try running with
./bin/my_app eval 'Release.Tasks.createdb()'
which follows this error:
** (KeyError) key :database not found in: [telemetry_prefix: [:my_app, :repo], otp_app: :my_app, timeout: 15000, pool_size: 10]
(elixir) lib/keyword.ex:393: Keyword.fetch!/2
(ecto_sql) lib/ecto/adapters/postgres.ex:128: Ecto.Adapters.Postgres.storage_up/1
lib/create_migrate_task.ex:57: Release.Tasks.ensure_repo_created/1
(elixir) lib/enum.ex:783: Enum."-each/2-lists^foreach/1-0-"/2
(elixir) lib/enum.ex:783: Enum.each/2
lib/create_migrate_task.ex:18: Release.Tasks.createdb/0
(stdlib) erl_eval.erl:680: :erl_eval.do_apply/6
note:
this is my config.exs: (I did not use run time configuration)
import Config
config :my_app,
ecto_repos: [MyApp.Repo]
config :school, MyApp.Repo,
database: "my-cool-db",
password: "changeme",
hostname: "123.456.8.789",
port: "5432",
timeout: 60_000,
pool_size: 10,
max_overflow: "100",
queue_target: 60_000,
queue_interval: 120_000
Trending in Questions
Hello!
Suppose you are building workflow (order / task / payment) processing system with the following requirements:
Each workflow con...
New
I’m aware of 2 such projects, are there others?
git: GitHub - team-alembic/realworld: A fullstack Phoenix LiveView application with back...
New
Hi all,
I’m working on a Phoenix project where I need to make external HTTP requests and I’m trying to choose between Req and HTTPoison....
New
How do I tell Hologram not to escape HTML when substituting into templates?
{Textile.render(@product.long_description)}
escapes the HTM...
New
I’d like to create a file with 600 permissions (rw-------), but there’s a race condition if I create it and then change the permissions. ...
New
Hi,
we run different LLM models across a cluster, with each node loading a configurable subset. Model-specific queues let nodes consume ...
New
When I use Mix.install with a git dependency, using git@github.com:... how do I change the SSH identity used?
I’ve got two Github accoun...
New
Other Trending Topics
Hey there,
I haven’t seen a list of useful Elixir specific skills for the popular AI tools yet so I’m starting one here with my first.
...
New
Hi everyone :waving_hand:
I wanted to share something I’ve been building — NowBlind, a random chat app designed to help people discover ...
New
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
(I just needed to vent somewhere and LinkedIn is full of hope, or hype, I’m not sure which exactly)
AI dream has many faces, but general...
New
Localize is the next generation localisation library for Elixir. Think of it as ex_cldr version 3.0. The first version will be released ...
New
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
- #code-sync
- #discussion
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #elixirconf-us
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #security
- #elixirconf-eu
- #api
- #forms
- #performance











Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
LostKobrakai
Production database are most often manually created, because security is more important. At best your app doesn’t have credentials for a user, which is allowed to create databases.
dinasol
@LostKobrakai I have a release that is deployed on various environments - dev, staging etc.. so it is necessary for me to have them created automatically on boot
here is my final code which worked well (also when having configuration in run time release.exs)
geofflangenderfer
this is a hole in the existing docs. It skips over creating prod databases.
How are you calling create_and_migrate() on your remote server?
Like this? ./bin/my_app eval ‘Release.Tasks.create_and_migrate()’