Collect, organize, and act on massive volumes of high-resolution data to power real-time intelligent systems. Learn more →
Phx_gen_auth Alternatives
Similar projects and alternatives to phx_gen_auth
-
-
CodeRabbit
CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
-
elixir_auth_google
👤Minimalist Google OAuth Authentication for Elixir Apps. Tested, Documented & Maintained. Setup in 5 mins. 🚀
-
-
credo
A static code analysis tool for the Elixir language with a focus on code consistency and teaching.
-
-
-
InfluxDB
InfluxDB high-performance time series database. Collect, organize, and act on massive volumes of high-resolution data to power real-time intelligent systems.
-
-
-
-
-
-
elixir-raknet
An Elixir client for the core of the RakNet networking protocol, useful for games and other latency-sensitive applications that typically rely on UDP
-
django-celery-docker-example
Discontinued Example Docker setup for a Django app behind an Nginx proxy with Celery workers
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
phx_gen_auth discussion
phx_gen_auth reviews and mentions
-
Build Interactive Phoenix LiveView UIs with Components
This code assumes you've used the Phoenix Auth generator to add authentication to your Phoenix app. The details of authentication aren't important for our purposes here. Just know that the survey route is a protected route that requires an authenticated user. This means that when a logged-in user points their browser at /survey, the SurveyLive view will mount with a session argument that contains a key of "user_token" pointing to a token we can use to identify the current user. The generator also gives us a function, Accounts.get_user_by_session_token(user_token), that we will use to fetch the user for that token.
-
LiveView Integration Tests in Elixir
We're also using a test helper provided for us by the Phoenix authentication generator—register_and_log_in_user/1. This function creates a conn struct with a logged-in user, a necessary step because visiting the /admin-dashboard route requires an authenticated user.
-
Best options for deploying your frontend and backend
Thanks for the suggestion. I started off with a Phoenix-only app but then I realised that it would be really nice to have a separate frontend. My Phoenix app was using phx.gen.auth, but according to the readme on their GH page, the `--no-html` option is not supported, so I'm thinking about trying POW. I've found this example which looks a little full-on, especially compared to how simple this is done in Django.
-
10 Years(-Ish) of Elixir
Thank you for your work on adding user registration and authorization to Phoenix!
I'm setting up a new Phoenix app for a side project this weekend and have just run Arron Renner's [auth generator](https://github.com/aaronrenner/phx_gen_auth). Having user registration out of the box will save a big chunk of time and energy!
-
How to connect Pow and Live View in your Phoenix project
Even though phx.gen.auth seems to be the hip solution for authentication at the moment in Phoenix land, I still prefer to use Pow for my small hobby projects and a side project I am working on. A short statement why I prefer Pow can be found at the end of the post.
-
A note from our sponsor - InfluxDB
influxdata.com | 18 Apr 2025
Stats
The primary programming language of phx_gen_auth is Elixir.
Popular Comparisons
- phx_gen_auth VS Pow
- phx_gen_auth VS elixir_auth_google
- phx_gen_auth VS ueberauth
- phx_gen_auth VS ueberauth_auth0
- phx_gen_auth VS ueberauth_active_directory
- phx_gen_auth VS PowAssent
- phx_gen_auth VS guardian
- phx_gen_auth VS phoenix_client_ssl
- phx_gen_auth VS github_oauth
- phx_gen_auth VS oauth2_facebook