apoorv-2204

apoorv-2204

Hi there Elixir Community,

IN the phoenix Endpoint, I want to have different session options for dev environment and the production environment, like setting cookie secure, etc.

Issue I am facing is when I use Application.get_env or Application.fetch_env it gives warning and CI fails ,
the Warning: is discouraged in the module body, use Application.compile_env/3 instead

When I use Compile env I get this error.

* (ArgumentError) could not fetch application environment [AdminWeb.Endpoint, :session_options] for application :admin because the application was not loaded nor configured
    (elixir 1.14.4) lib/application.ex:602: Application.compile_env!/3
    lib/admin_web/endpoint.ex:5: (module)
    (elixir 1.14.4) lib/kernel/parallel_compiler.ex:340: anonymous fn/5 in Kernel.ParallelCompiler.spawn_workers/7
Elixir

I have two apps in umbrella
AdminWeb and ServiceProviderWeb

Code for AdminWeb ,ServiceProvider


defmodule AdminWeb.Endpoint do
  @moduledoc false
  use Phoenix.Endpoint, otp_app: :admin

  @session_options Application.compile_env!(:admin, [__MODULE__, :session_options])

  socket("/admin/live", Phoenix.LiveView.Socket,
    websocket: [connect_info: [session: @session_options]]
  )
#other lines omitted
  plug(Plug.Session, @session_options)
end

defmodule ServiceProvider.Endpoint do
  @moduledoc false
  use Phoenix.Endpoint, otp_app: :service_provider
  @session_options Application.compile_env!(:service_provider, [__MODULE__, :session_options])


  socket("/service_provider/live", Phoenix.LiveView.Socket,
    websocket: [connect_info: [session: @session_options]]
  )

  plug(Plug.Session, @session_options)

end
 

dev.exs

 
config :admin, AdminWeb.Endpoint,
  server: true,
  http: [port: 4001],
  debug_errors: true,
  code_reloader: true,
  check_origin: false,
  watchers: [
    node: [
      "node_modules/webpack/bin/webpack.js",
      "--mode",
      "development",
      cd: Path.expand("../apps/admin/assets", __DIR__)
    ]
  ],
  live_reload: [
    patterns: [
      ~r"priv/static/.*(js|css|png|jpeg|jpg|gif|svg)$",
      ~r"priv/gettext/.*(po)$",
      ~r"lib/admin_web/.*(ex)$",
      ~r"lib/admin_web/.*(eex)$",
      ~r"lib/admin_web/.*(heex)$"
    ],
    url: "/admin/phoenix/live_reload/socket"
  ],
  session_options: [
    max_age: 120 * 60 * 60,
    store: AdminWeb.Session.Store,
    key: "_a_dev_web_key_",
    signing_salt:  "rand_Contatvalie"
  ]

config :service_provider, ServiceProvider.Endpoint,
  server: true,
  http: [port: 4003],
  debug_errors: true,
  code_reloader: true,
  check_origin: false,
  watchers: [
    node: [
      "node_modules/webpack/bin/webpack.js",
      "--mode",
      "development",
      cd: Path.expand("../apps/service_provider/assets", __DIR__)
    ]
  ],
  live_reload: [
    patterns: [
      ~r"priv/static/.*(js|css|png|jpeg|jpg|gif|svg)$",
      ~r"priv/gettext/.*(po)$",
      ~r"lib/service_provider/.*(ex)$",
      ~r"lib/service_provider/.*(eex)$",
      ~r"lib/service_provider/.*(heex)$"
    ],
    url: "/service_provider/phoenix/live_reload/socket"
  ],
  session_options: [
    store: :cookie,
    key: "_sp_dev_web_key_",
    signing_salt: "rand_Constant tvallue",
    max_age: 120 * 60 * 60
  ]

Prod.exs

config :admin, AdminWeb.Endpoint,
  cache_static_manifest: "priv/static/cache_manifest.json",
  session_options: [
    max_age: 120 * 60 * 60,
    store: AdminWeb.Session.Store,
    key: "_a_web_key_",
    signing_salt: "random_sallt",
    secure: true,
    http_only: true,
    sign: true
  ]

config :service_provider, ServiceProvider.Endpoint,
  cache_static_manifest: "priv/static/cache_manifest.json",
  session_options: [
    store: :cookie,
    key: "_sp_web_key_",
    signing_salt: "random_sallt",
    max_age: 120 * 60 * 60,
    secure: true,
    http_only: true,
    sign: true,encrypt: true
  ]
`My questions`

Q1. What is the solution for it, what mistake I am making?.What wrong settings I have done here?
Q2. Are dev.exs and prod.exs executed once on compilation? so can i use `Base.encode64(:crypto.strong_rand_bytes(64), padding: false)` for `signing_salt`.
Q3. what are the generral best practices tips that you guys can share?

Showing Posts 1 to 3

apoorv-2204

apoorv-2204 OP

elixir 1.14.4-otp-25
erlang 25.2.2

linux
already tried pruging _build , deps, plts,etc

gushonorato

gushonorato

Hey @apoorv-2204

Q1. What is the solution for it, what mistake I am making?.What wrong settings I have done here?

The problem is that Application.compile_env!/3 does not accept a list as an argument. Instead, you should do the following: @session_options Application.compile_env!(:admin, ServiceProvider.Endpoint) |> Keyword.fetch!(:session_options)

Q2. Are dev.exs and prod.exs executed once on compilation? so can i use Base.encode64(:crypto.strong_rand_bytes(64), padding: false) for signing_salt.

You must not use Base.encode64/2 to generate the signing_salt in this way. If you do so, a new signing_salt will be generated with each deployment, and all sessions will be invalidated in production every time the application is deployed.

Q3. what are the generral best practices tips that you guys can share?

You can use any signing_salt for development and store it hardcoded in your dev.exs file. However, for production, it is not recommended to store the signing_salt hardcoded in version-controlled files. Instead, store it as an environment variable and load it in config/runtime.exs.

# config/runtime.exs

signing_salt = 
  System.get_env("SESSION_SIGNING_SALT") || 
    raise "SESSION_SIGNING_SALT environment variable is not set"

config :admin, AdminWeb.Endpoint,
  session_options: [
    max_age: 120 * 60 * 60,
    store: AdminWeb.Session.Store,
    key: "_a_dev_web_key_",
    signing_salt: signing_salt
  ]
apoorv-2204

apoorv-2204 OP

thanks a lot sir
it solved my issue
@session_options Application.compile_env!(:admin, ServiceProvider.Endpoint) |> Keyword.fetch!(:session_options)

— All posts loaded —

Where Next? Top

Trending in Discussions Top

AstonJ
As the title says, please share what you’ve been up to with Elixir. Whether that’s been learning it, looking into it, making stuff with i...
2977 94592 917
New
cblavier
Hey there, It’s been more than a year since we started using LiveView as our main UI library and building a whole library of UI componen...
New
mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
heathen
Quite interesting article Google brought me. Didn’t find any mentions about it here. What do you think in general? Would you use togethe...
New
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
New
AstonJ
Since we have deprecated our Erlang sections (as we have dedicated Erlang Forums now) let’s add this thread for those who’d like to post ...
New
maennchen
:warning: Security advisory: Decimal DoS vulnerability A vulnerability has been published for decimal where very large exponents can cau...
New

Other Trending Topics Top

JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
marciok
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
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
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
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
webofbits
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself. My main conc...
#ai
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews