con un clic
reset-local-env
Reset Auth9 local Docker development environment to a clean state.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Menú
Reset Auth9 local Docker development environment to a clean state.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Run E2E tests for Auth9 portal using Playwright with hybrid testing strategy.
Run tests, check logs, and troubleshoot Auth9 services in Docker and Kubernetes environments.
Run performance benchmarks for auth9-core API using hey load testing tool.
Execute scenario-based QA testing with browser automation, database validation, and automatic ticket creation for failures.
Rust coding conventions and patterns for auth9-core development.
Run tests and check coverage for Auth9 backend, frontend, and SDK with mock-based testing patterns.
| name | reset-local-env |
| description | Reset Auth9 local Docker development environment to a clean state. |
Reset Auth9 local Docker development environment.
Use this when:
Run the reset script to get a clean local environment:
./scripts/reset-docker.sh
This script performs:
After reset, use these credentials:
| Service | URL | Username | Password |
|---|---|---|---|
| Admin Portal | http://localhost:3000 | admin@auth9.local | SecurePass123! |
cd /path/to/auth9
COMPOSE_FILES="-f docker-compose.yml -f docker-compose.observability.yml"
# Stop and remove containers
docker-compose $COMPOSE_FILES down --remove-orphans
# Remove images
docker rmi auth9-auth9-core auth9-auth9-portal
# Remove volumes
docker volume rm auth9_tidb-data auth9_redis-data auth9_prometheus-data auth9_grafana-data auth9_loki-data auth9_tempo-data
# Rebuild and start
docker-compose $COMPOSE_FILES build --no-cache
docker-compose $COMPOSE_FILES up -d
# Wait for services
sleep 30
docker-compose $COMPOSE_FILES ps
| Service | Port | Purpose |
|---|---|---|
| auth9-portal | 3000 | Admin dashboard |
| auth9-core | 8080 | REST API + /metrics |
| auth9-core | 50051 | gRPC |
| auth9-oidc | — | Built-in OIDC engine |
| tidb | 4000 | Database |
| redis | 6379 | Cache |
| prometheus | 9090 | Metrics collection |
| grafana | 3001 | Dashboards |
| loki | 3100 | Log aggregation |
| tempo | 3200/4317 | Distributed tracing |
After reset, verify services are healthy:
# Check all containers are running
docker-compose ps
# Test API health endpoint
curl http://localhost:8080/health
# Test portal is accessible
curl http://localhost:3000
# Check database connection
docker exec auth9-tidb mysql -e "SHOW DATABASES;"
# Check Redis
docker exec auth9-redis redis-cli ping
# Check logs
docker-compose logs
# Check specific service
docker logs auth9-core
# Check what's using the ports
lsof -i :3000
lsof -i :8080
lsof -i :4000
# Kill conflicting processes or change ports in docker-compose.yml
# Remove volumes with sudo if needed
docker volume ls
sudo docker volume rm auth9_tidb-data auth9_redis-data auth9_prometheus-data auth9_grafana-data auth9_loki-data auth9_tempo-data