earth7316

earth7316

I’m starting a new Phoenix 1.3 application and following along with the PragProg book for authentication. The book says to put auth.ex plug code into the controllers directory. Is that still the canonical directory to put plugs? That kind of makes sense to me but after years of rails development I fear a pollution of the controller directory with plugs over time. :slight_smile: Does the conventional wisdom for Phoenix 1.3 and the use of contexts change anything in this regard? I was wondering if putting auth.ex in my accounts directory (accounts being my context with users under it).

Thanks for any tips.

Showing Posts 1 to 4

idi527

idi527

I put them in the lib/web/plugs folder.

earth7316

earth7316 OP

So in Phx 1.3 final that would be
lib/my_app_web/plugs

alongside the controllers, channels, etc directories?

idi527

idi527

Yeah, I guess.

I usually call the “web interface” otp app just that, web, so for me it’s apps/web/lib/web/plugs actually. But that’s only relevant if you structure your app as an umbrella project.

earth7316

earth7316 OP

+1 - thanks!

— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
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
kszambelanczyk
Hello! Could someone please give me a help/sample code, how to delete a file from s3 using waffle/waffle_ecto from Phoenix app. I creat...
New
RemyXRenard
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
velrest
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
samoloth
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
FlyingNoodle
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
ryanwinchester
apply_graft/2 doesn’t rewrite an add_many sub-workflow’s deps on an add step. Grafted jobs cancel with “upstream job was deleted” Version...
New

Other Trending Topics Top

webofbits
Aludel 0.7.0 is released :tada: Since 0.5.0, Aludel has grown into a much more complete LLM evaluation toolkit for Elixir and Phoenix app...
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
garrison
Hobbes is a low-level distributed database for the Elixir programming language. Hobbes provides a simple, safe, and scalable storage lay...
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

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews