Nexus 5 - armv7
staymetal
James_E
That solution has bit rot; the packages it recommends are no longer maintained and pin some shared dependencies with Phoenix which have since undergone breaking updates, so you’ll get an error like this:
Because
phoenix_live_dashboard >= 0.5.0depends onecto ~> 3.6.2 or ~> 3.7andsqlite_ecto >= 1.0.0 and < 1.1.0depends onecto ~> 1.0,phoenix_live_dashboard >= 0.5.0is incompatible withsqlite_ecto >= 1.0.0 and < 1.1.0.
And because your app depends onphoenix_live_dashboard ~> 0.8.3,sqlite_ecto >= 1.0.0 and < 1.1.0is forbidden.
So, because your app depends onsqlite_ecto ~> 1.0.0, version solving failed.
Here’s the solution for OP’s request in 2024, for posterity / because this thread is still floating to the top of Google:
# in mix.exs
defp deps do
[
…
{:ecto_sqlite3, "~> 0.17.4"},
…
]
end
# in config/dev.exs
config :myApp, MyApp.Repo,
adapter: Ecto.Adapters.SQLite3,
database: "./dev.db",
stacktrace: true,
show_sensitive_data_on_connection_error: true
# in config/test.exs
config :myApp, MyApp.Repo,
adapter: Ecto.Adapters.SQLite3,
database: "./test#{System.get_env("MIX_TEST_PARTITION")}.db",
pool: Ecto.Adapters.SQL.Sandbox,
pool_size: System.schedulers_online() * 2
# in lib/myApp/repo.ex
defmodule MyApp.Repo do
use Ecto.Repo,
otp_app: :myApp,
adapter: Ecto.Adapters.SQLite3
end
3
LostKobrakai
Phoenix can generate that with mix phx.new --database sqlite3. No need to manually do that.
5
ariandanim
I facing some difficult in production mode when using sqlite3, heres my step in vps production, still need help does it all righ the url database sqlite3 or not
- export SECRET_KEY_BASE=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
- export DATABASE_URL=ecto://var/www/myweb.com/myweb/myapp_prod.db
- mix deps.get --only prod
- MIX_ENV=prod mix compile
- MIX_ENV=prod mix assets.deploy
- PORT=4000 MIX_ENV=prod mix phx.server
At the end when hit enter after typing the number 6 command, my production code showing error like this :
23:49:12.502 [notice] Application mywebapp exited: Myweb.Application.start(:normal, []) returned an error: shutdown: failed to start child: Myweb.Repo
** (EXIT) an exception was raised:
** (Ecto.InvalidURLError) invalid URL ecto://var/www/myweb.com/mywebapp/mywebdb_prod.db, path should be a database name. The parsed URL is: %URI{scheme: "ecto", authority: "var", userinfo: nil, host: "var", port: nil, path: "/www/myweb.com/mywebapp/mywebdb_prod.db", query: nil, fragment: nil}
(ecto 3.12.4) lib/ecto/repo/supervisor.ex:111: Ecto.Repo.Supervisor.parse_url/1
(ecto 3.12.4) lib/ecto/repo/supervisor.ex:29: Ecto.Repo.Supervisor.init_config/4
(ecto 3.12.4) lib/ecto/repo/supervisor.ex:190: Ecto.Repo.Supervisor.init/1
(stdlib 6.1.2) supervisor.erl:869: :supervisor.init/1
(stdlib 6.1.2) gen_server.erl:2229: :gen_server.init_it/2
(stdlib 6.1.2) gen_server.erl:2184: :gen_server.init_it/6
(stdlib 6.1.2) proc_lib.erl:329: :proc_lib.init_p_do_apply/3
** (exit) :terminating
(kernel 10.1.1) application_controller.erl:511: :application_controller.call/2
(kernel 10.1.1) application.erl:367: :application."-ensure_all_started/3-lc$^0/1-0-"/1
(kernel 10.1.1) application.erl:367: :application.ensure_all_started/3
(mix 1.17.3) lib/mix/tasks/app.start.ex:72: Mix.Tasks.App.Start.start/3
(mix 1.17.3) lib/mix/task.ex:495: anonymous fn/3 in Mix.Task.run_task/5
(mix 1.17.3) lib/mix/tasks/run.ex:129: Mix.Tasks.Run.run/5
(mix 1.17.3) lib/mix/tasks/run.ex:85: Mix.Tasks.Run.run/1
(mix 1.17.3) lib/mix/task.ex:495: anonymous fn/3 in Mix.Task.run_task/5
0
kokolegorille
An easy way to check the config would be to create a side project with --database sqlite3.
You would see DATABASE_URL is not used, but DATABASE_PATH
You would find this code…
database_path =
System.get_env("DATABASE_PATH") ||
raise """
environment variable DATABASE_PATH is missing.
For example: /etc/kokolite/kokolite.db
"""
Which means You need to adapt your config/runtime.exs to sqlite3
No, it is really not the way to start a release… You need to set all the required env variables and use the release script.
Once You know how to start the release, You’ll need to write a service script for systemd, if You are on Linux.
It’s hard to deploy a release, but only the first time…
Then, You’ll learn that deploying nodes in a cluster is even much harder 
2