better_auth 0.1.1 → 0.3.0

data/CONTRIBUTING.md

@@ -1,187 +0,0 @@
-# Contributing to Better Auth Ruby
-
-Thank you for your interest in contributing to Better Auth Ruby!
-This guide will help you get started with the contribution process.
-
-## Code of Conduct
-
-This project and everyone participating in it is governed by our
-[Code of Conduct](/CODE_OF_CONDUCT.md).
-By participating, you are expected to uphold this code.
-
-## Project Structure
-
-```
-lib/
-  better_auth.rb              # Main entry point
-  better_auth/
-    version.rb                # Version constant
-    core.rb                   # Core module loader
-    core/                     # Core authentication logic
-    rails.rb                  # Rails adapter entry
-    rails/                    # Rails-specific code
-
-test/                       # Core library tests (Minitest)
-spec/                       # Rails adapter tests (RSpec)
-```
-
-## Development Guidelines
-
-When contributing to Better Auth Ruby:
-
-* Keep changes focused. Large PRs are harder to review.
-* Follow Ruby conventions and idioms
-* Ensure all code passes StandardRB linting
-* Write tests for new features
-* Maintain backward compatibility when possible
-
-## Getting Started
-
-1. Fork the repository to your GitHub account
-
-2. Clone your fork locally:
-
-   ```bash
-   git clone https://github.com/your-username/better-auth-ruby.git
-   cd better-auth-ruby
-   ```
-
-3. Install Ruby (3.2+ required, 3.3 recommended)
-
-   We recommend using a Ruby version manager like rbenv, rvm, or asdf.
-
-4. Install dependencies:
-
-   ```bash
-   bundle install
-   ```
-
-5. Run tests to ensure everything is working:
-
-   ```bash
-   bundle exec rake ci
-   ```
-
-## Development Workflow
-
-1. Create a new branch for your changes:
-
-   ```bash
-   git checkout -b type/description
-   # Example: git checkout -b feat/oauth-provider
-   ```
-
-   Branch type prefixes:
-
-   * `feat/` - New features
-   * `fix/` - Bug fixes
-   * `docs/` - Documentation changes
-   * `refactor/` - Code refactoring
-   * `test/` - Test-related changes
-   * `chore/` - Build process or tooling changes
-
-2. Make your changes following the code style guidelines
-
-3. Run the linter:
-
-   ```bash
-   bundle exec standardrb --fix
-   ```
-
-4. Add tests for your changes
-
-5. Run the test suite:
-
-   ```bash
-   # Run all tests
-   bundle exec rake ci
-
-   # Run only core tests
-   bundle exec rake test
-
-   # Run only Rails adapter tests
-   bundle exec rspec
-   ```
-
-6. Commit your changes with a descriptive message:
-
-   ```text
-   feat(rails): add current_user helper method
-
-   fix(core): resolve token validation issue
-   ```
-
-7. Push your branch to your fork
-
-8. Open a pull request against the **main** branch
-
-## Code Style
-
-We use [StandardRB](https://github.com/standardrb/standard) for code formatting and linting.
-Before committing, please ensure your code passes:
-
-```bash
-# Check code style
-bundle exec standardrb
-
-# Auto-fix issues
-bundle exec standardrb --fix
-```
-
-### Ruby Style Guidelines
-
-* Use 2 spaces for indentation
-* Use `snake_case` for methods, variables, and file names
-* Use `CamelCase` for classes and modules
-* Use `SCREAMING_SNAKE_CASE` for constants
-* Add `frozen_string_literal: true` pragma to all Ruby files
-* Prefer single quotes for strings without interpolation
-* Avoid unnecessary Ruby features (unless they improve readability)
-
-## Testing Guidelines
-
-### Core Library (Minitest)
-
-Located in `test/` directory:
-
-```ruby
-# test/better_auth/some_feature_test.rb
-require_relative "test_helper"
-
-class SomeFeatureTest < Minitest::Test
-  def test_something
-    assert_equal expected, actual
-  end
-end
-```
-
-### Rails Adapter (RSpec)
-
-Located in `spec/` directory:
-
-```ruby
-# spec/better_auth/rails/some_feature_spec.rb
-require "spec_helper"
-
-RSpec.describe BetterAuth::Rails::SomeFeature do
-  it "does something" do
-    expect(subject).to eq expected
-  end
-end
-```
-
-## Pull Request Process
-
-1. Create a draft pull request early to facilitate discussion
-2. Reference any related issues in your PR description
-3. Ensure all tests pass and the build is successful
-4. Update documentation as needed
-5. Keep your PR focused on a single feature or bug fix
-6. Be responsive to code review feedback
-
-## Security Issues
-
-For security-related issues, please email [security@better-auth.com](mailto:security@better-auth.com).
-Include a detailed description of the vulnerability and steps to reproduce it.
-All reports will be reviewed and addressed promptly.
-For more information, see our [security documentation](/SECURITY.md).

data/Gemfile

@@ -1,12 +0,0 @@
-source "https://rubygems.org"
-
-ruby file: ".ruby-version"
-
-gemspec
-
-group :development, :test do
-  gem "standardrb", "~> 1.0"
-  gem "minitest", "~> 5.25"
-  gem "rake", "~> 13.2"
-  gem "simplecov", "~> 0.22", require: false
-end

data/Makefile

@@ -1,207 +0,0 @@
-# Better Auth Ruby - Makefile
-# Este archivo te ayuda a ejecutar comandos comunes de desarrollo
-# Cada comando tiene comentarios explicativos para aprender
-
-# Variables de color para hacer la salida más legible
-BLUE := \033[36m
-GREEN := \033[32m
-YELLOW := \033[33m
-NC := \033[0m # No Color
-
-# =============================================
-# COMANDOS PRINCIPALES DE DESARROLLO
-# =============================================
-
-# Instala todas las dependencias del proyecto
-# Equivale a: bundle install
-.PHONY: install
-install:
-	@echo "$(BLUE)📦 Instalando dependencias...$(NC)"
-	bundle install
-	@echo "$(GREEN)✓ Dependencias instaladas$(NC)"
-
-# Configuración inicial del proyecto (primer clone)
-# Ejecuta bin/setup que hace bundle install
-.PHONY: setup
-setup:
-	@echo "$(BLUE)🔧 Configurando proyecto...$(NC)"
-	bin/setup
-	@echo "$(GREEN)✓ Proyecto configurado$(NC)"
-
-# =============================================
-# COMANDOS DE CALIDAD DE CÓDIGO
-# =============================================
-
-# Revisa que el código cumpla con el estilo StandardRB
-# Muestra errores pero NO los corrige automáticamente
-.PHONY: lint
-lint:
-	@echo "$(BLUE)🔍 Revisando estilo de código...$(NC)"
-	bundle exec standardrb
-	@echo "$(GREEN)✓ Código cumple con el estilo$(NC)"
-
-# Revisa Y AUTOCORRIGE problemas de estilo con StandardRB
-# Úsalo cuando quieras formatear todo automáticamente
-.PHONY: lint-fix
-lint-fix:
-	@echo "$(BLUE)🔧 Corrigiendo estilo de código automáticamente...$(NC)"
-	bundle exec standardrb --fix
-	@echo "$(GREEN)✓ Código corregido$(NC)"
-
-# =============================================
-# COMANDOS DE TESTING
-# =============================================
-
-# Ejecuta TODOS los tests (core + rails adapter)
-# Es lo mismo que: bundle exec rake ci
-.PHONY: test
-test:
-	@echo "$(BLUE)🧪 Ejecutando todos los tests...$(NC)"
-	bundle exec rake test
-	@echo "$(GREEN)✓ Tests completados$(NC)"
-
-# Ejecuta solo los tests del core (Minitest)
-# Son los tests en el directorio test/
-.PHONY: test-core
-test-core:
-	@echo "$(BLUE)🧪 Ejecutando tests del core...$(NC)"
-	bundle exec rake test:core
-	@echo "$(GREEN)✓ Tests del core completados$(NC)"
-
-# Ejecuta solo los tests del adapter Rails (RSpec)
-# Son los tests en el directorio spec/
-.PHONY: test-rails
-test-rails:
-	@echo "$(BLUE)🧪 Ejecutando tests del adapter Rails...$(NC)"
-	bundle exec rspec
-	@echo "$(GREEN)✓ Tests de Rails completados$(NC)"
-
-# Ejecuta tests con cobertura de código
-# Genera reporte en coverage/index.html
-.PHONY: test-coverage
-test-coverage:
-	@echo "$(BLUE)📊 Ejecutando tests con cobertura...$(NC)"
-	COVERAGE=true bundle exec rake test
-	@echo "$(GREEN)✓ Reporte de cobertura en coverage/index.html$(NC)"
-
-# =============================================
-# COMANDOS DE INTEGRACIÓN CONTINUA (CI)
-# =============================================
-
-# Ejecuta TODO el pipeline de CI localmente
-# 1. Lint (StandardRB)
-# 2. Tests (Minitest + RSpec)
-# Esto es lo que corre GitHub Actions en cada PR
-.PHONY: ci
-ci:
-	@echo "$(BLUE)🔧 Ejecutando CI completo...$(NC)"
-	bundle exec rake ci
-	@echo "$(GREEN)✓ CI completado exitosamente$(NC)"
-
-# =============================================
-# COMANDOS DE DESARROLLO INTERACTIVO
-# =============================================
-
-# Abre una consola interactiva (IRB) con la gema cargada
-# Útil para probar código manualmente
-.PHONY: console
-console:
-	@echo "$(BLUE)💻 Abriendo consola interactiva...$(NC)"
-	bin/console
-
-# =============================================
-# COMANDOS DE PUBLICACIÓN (RELEASE)
-# =============================================
-
-# PASO 1: Actualiza la versión en version.rb
-# Debes hacerlo manualmente antes de release
-
-# PASO 2: Crea un git tag con la versión
-# Ejemplo: make tag VERSION=0.1.0
-.PHONY: tag
-tag:
-ifndef VERSION
-	$(error VERSION no está definido. Usa: make tag VERSION=0.1.0)
-endif
-	@echo "$(YELLOW)🏷️  Creando tag v$(VERSION)...$(NC)"
-	git add -A
-	git commit -m "chore: release v$(VERSION)"
-	git tag -a v$(VERSION) -m "Release v$(VERSION)"
-	@echo "$(GREEN)✓ Tag creado. Ahora haz: git push origin main --tags$(NC)"
-
-# PASO 3 (MANUAL): Publica la gema a RubyGems manualmente
-# Solo úsalo si NO estás usando GitHub Actions
-.PHONY: release-manual
-release-manual:
-	@echo "$(YELLOW)📦 Construyendo gema...$(NC)"
-	gem build better_auth.gemspec
-	@echo "$(YELLOW)🚀 Publicando a RubyGems...$(NC)"
-	gem push better_auth-*.gem
-	@echo "$(GREEN)✓ Gema publicada$(NC)"
-
-# =============================================
-# COMANDOS DE BASES DE DATOS (TESTING)
-# =============================================
-
-# Inicia los contenedores de Docker para testing
-# (PostgreSQL, MySQL, Redis)
-.PHONY: db-up
-db-up:
-	@echo "$(BLUE)🐳 Iniciando bases de datos...$(NC)"
-	docker-compose up -d
-	@echo "$(GREEN)✓ Bases de datos listas$(NC)"
-
-# Detiene los contenedores de Docker
-.PHONY: db-down
-db-down:
-	@echo "$(BLUE)🐳 Deteniendo bases de datos...$(NC)"
-	docker-compose down
-	@echo "$(GREEN)✓ Bases de datos detenidas$(NC)"
-
-# =============================================
-# COMANDOS DE LIMPIEZA
-# =============================================
-
-# Limpia archivos temporales y la gema compilada
-.PHONY: clean
-clean:
-	@echo "$(BLUE)🧹 Limpiando archivos temporales...$(NC)"
-	rm -rf *.gem coverage/ .bundle/
-	@echo "$(GREEN)✓ Limpieza completada$(NC)"
-
-# =============================================
-# AYUDA
-# =============================================
-
-# Muestra todos los comandos disponibles con descripción
-.PHONY: help
-help:
-	@echo "$(GREEN)Better Auth Ruby - Comandos disponibles:$(NC)"
-	@echo ""
-	@echo "$(YELLOW)Instalación:$(NC)"
-	@echo "  make install       - Instala dependencias (bundle install)"
-	@echo "  make setup         - Configuración inicial del proyecto"
-	@echo ""
-	@echo "$(YELLOW)Desarrollo:$(NC)"
-	@echo "  make console       - Abre consola interactiva (IRB)"
-	@echo "  make lint          - Revisa estilo de código"
-	@echo "  make lint-fix      - Corrige estilo automáticamente"
-	@echo ""
-	@echo "$(YELLOW)Testing:$(NC)"
-	@echo "  make test          - Ejecuta todos los tests"
-	@echo "  make test-core     - Solo tests del core (Minitest)"
-	@echo "  make test-rails    - Solo tests Rails (RSpec)"
-	@echo "  make test-coverage - Tests con reporte de cobertura"
-	@echo "  make ci            - Ejecuta CI completo (lint + test)"
-	@echo ""
-	@echo "$(YELLOW)Bases de datos (Docker):$(NC)"
-	@echo "  make db-up         - Inicia PostgreSQL, MySQL, Redis"
-	@echo "  make db-down       - Detiene contenedores"
-	@echo ""
-	@echo "$(YELLOW)Release:$(NC)"
-	@echo "  make tag VERSION=x.x.x  - Crea git tag para release"
-	@echo "  make release-manual     - Publica manualmente (NO usar con CI)"
-	@echo ""
-	@echo "$(YELLOW)Utilidades:$(NC)"
-	@echo "  make clean         - Limpia archivos temporales"
-	@echo "  make help          - Muestra esta ayuda"

data/Rakefile

@@ -1,25 +0,0 @@
-# frozen_string_literal: true
-
-require "bundler/gem_tasks"
-require "rake/testtask"
-
-Rake::TestTask.new(:test) do |t|
-  t.libs << "test"
-  t.libs << "lib"
-  t.test_files = FileList["test/**/*_test.rb"]
-end
-
-desc "Run StandardRB linter"
-task :lint do
-  sh "bundle exec standardrb"
-end
-
-desc "Auto-fix StandardRB issues"
-task "lint:fix" do
-  sh "bundle exec standardrb --fix"
-end
-
-desc "Run full CI check (lint + test)"
-task ci: [:lint, :test]
-
-task default: :ci

data/SECURITY.md

@@ -1,28 +0,0 @@
-# Security Policy
-
-### Reporting a Vulnerability
-
-If you believe you've found a security vulnerability, please follow these steps:
-
-1. Do not disclose the vulnerability publicly until it has been addressed by our
-   team.
-2. Email your findings to `security@better-auth.com` Include:
-   * A description of the vulnerability
-   * Steps to reproduce the vulnerability
-   * Potential impact of the vulnerability
-   * Any suggestions for mitigation
-   * Any other relevant information
-3. We will respond to your report within 72 hours.
-4. If the issue is confirmed, we will release a patch as soon as possible.
-
-### Disclosure Policy
-
-If the issue is confirmed, we will release a patch as soon as possible.
-Once a patch is released, we will disclose the issue publicly.
-If 90 days has elapsed and we still don't have a fix, we will disclose the issue
-publicly.
-
-## Supported Versions
-
-We only support the latest version of Better Auth Ruby.
-Older versions are not supported.

data/docker-compose.yml

@@ -1,63 +0,0 @@
-# Services for testing database adapters
-# These are used in CI for testing various database backends
-
-x-postgres-healthcheck: &postgres-healthcheck
-  healthcheck:
-    test: ["CMD-SHELL", "pg_isready -U user -d better_auth"]
-    interval: 1s
-    timeout: 5s
-    retries: 10
-
-x-mysql-healthcheck: &mysql-healthcheck
-  healthcheck:
-    test: ["CMD", "mysqladmin", "ping", "-h", "127.0.0.1", "-uuser", "-ppassword"]
-    interval: 1s
-    timeout: 5s
-    retries: 10
-    start_period: 30s
-
-services:
-  redis:
-    image: redis:latest
-    container_name: redis
-    ports:
-      - "6379:6379"
-    volumes:
-      - redis_data:/data
-    healthcheck:
-      test: ["CMD", "redis-cli", "ping"]
-      interval: 1s
-      timeout: 5s
-      retries: 10
-
-  postgres:
-    <<: *postgres-healthcheck
-    image: postgres:latest
-    container_name: postgres
-    environment:
-      POSTGRES_USER: user
-      POSTGRES_PASSWORD: password
-      POSTGRES_DB: better_auth
-    ports:
-      - "5432:5432"
-    volumes:
-      - postgres_data:/var/lib/postgresql
-
-  mysql:
-    <<: *mysql-healthcheck
-    image: mysql:latest
-    container_name: mysql
-    environment:
-      MYSQL_ROOT_PASSWORD: root_password
-      MYSQL_DATABASE: better_auth
-      MYSQL_USER: user
-      MYSQL_PASSWORD: password
-    ports:
-      - "3306:3306"
-    volumes:
-      - mysql_data:/var/lib/mysql
-
-volumes:
-  redis_data:
-  postgres_data:
-  mysql_data: