You must set ELECTRIC_SECRET

Open
#1 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
docker-compose, elixir
Domain
devops

Research direction

Start by running docker compose up and inspect the Compose configuration for the Electric environment variables. Read the reported validation point in lib/electric/config.ex and the referenced runtime.exs entry point to understand the required setting. Done means the setup instructions and configuration let the example start securely, or clearly document the required development-only alternative.

Written by the indexing model from the issue text.

Description

Following instructions when I run docker compose up I see

Runtime terminating during boot ({#{message=><<"You must set ELECTRIC_SECRET unless ELECTRIC_INSECURE=true. Setting ELECTRIC_INSECURE=true risks exposing your database, only use insecure mode in development or you've otherwise secured the Electric API">>,'__struct__'=>'Elixir.RuntimeError','__exception__'=>true},[{'Elixir.Electric.Config','validate_security_config!',2,[{file,"lib/electric/config.ex"},{line,411},{error_info,#{module=>'Elixir.Exception'}}]},{elixir_eval,'__FILE__',1,[{file,"/app/releases/1.0.20/runtime.exs"},{line,172}]},{elixir,eval_external_handler,3,[{file,"src/elixir.erl"},{line,386}]},{erl_eval,do_apply,7,[{file,"erl_eval.erl"},{line,919}]},{erl_eval,exprs,6,[{file,"erl_eval.erl"},{line,271}]},{elixir,eval_forms,4,[{file,"src/elixir.erl"},{line,364}]},{'Elixir.Module.ParallelChecker',verify,1,[{file,"lib/module/parallel_checker.ex"},{line,120}]},{'Elixir.Code',validated_eval_string,3,[{file,"lib/code.ex"},{line,572}]}]})
Dominant language
TypeScript
Stars
7
Forks
1
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.