Question 1

How to add social login like Google or Facebook to Addict?

Accepted Answer

Addict doesn't natively support OAuth or social logins; you'd need to integrate a separate library such as Ueberauth and manually handle the authentication flow alongside Addict's email/password system.

Question 2

Addict vs Guardian for Phoenix authentication?

Accepted Answer

Addict is simpler and focused on session-based email/password auth with quick setup, while Guardian is more feature-rich, supporting JWT tokens and OAuth, but requires more configuration. Choose Addict for basic needs, Guardian for advanced scenarios.

Question 3

How to customize the password reset email template in Addict?

Accepted Answer

Since Addict uses configurable mailers, you can override default templates by implementing a custom mailer per the README's guidelines or modifying the generated boilerplate files in your app.

Question 4

Does Addict handle email verification for new user registrations?

Accepted Answer

No, Addict's core features are registration, login, logout, and password recovery; email verification isn't included, so you'd need to add it manually using Ecto callbacks or extensions.

Question 5

How to use Addict with a Phoenix app that has a different database schema for users?

Accepted Answer

Addict requires specific fields in the user model; if your schema differs, adapt it by adding the required fields or use Ecto changesets to map data, but this may involve extra boilerplate code.

Question 6

What are the security best practices when using Addict's authentication plug?

Accepted Answer

Ensure you use HTTPS in production, set secure session cookies, and regularly update dependencies, as Addict relies on Phoenix's session management which should be configured with encryption and proper timeouts.

addict

What is addict?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions