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
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
Hello,
I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
Other Trending Topics
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself.
My main conc...
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
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










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()’