A modern single-player implementation of the popular Exploding Kittens card game with user authentication and leaderboards.

• Single Player Game - Draw cards and avoid exploding kittens
• User Authentication - JWT-based registration and login
• Score Tracking - Personal scores and global leaderboard
• Flexible Storage - Redis or in-memory storage via configuration
• Responsive Design - Works on all screen sizes (100vh/100vw)
• Real-time Feedback - Toast notifications for all actions

Backend: Go + Gin + Redis/Memory Storage
Frontend: React + Vite + Redux + Framer Motion
Database: Redis (production) / In-Memory (free tier)
Deployment: Render + Vercel

• Interface-based design - Single codebase supports multiple storage types
• Environment-driven - Switch storage via USE_MEMORY_STORE variable
• Production ready - Redis for persistence, Memory for free deployment

• Go 1.21+
• Node.js 18+
• Redis (for local development)

1. Clone and setup

git clone https://github.com/yourusername/exploding-kittens.git cd exploding-kittens

2. Test with Redis (Recommended)

# Start Redis docker-compose up -d redis # Backend with Redis cd backend cp .env.example .env # Edit .env: USE_MEMORY_STORE=false go mod tidy # Set environment and run $env:USE_MEMORY_STORE="false"; go run main.go # Frontend cd ../frontend cp .env.example .env npm install npm run dev

3. Test with Memory Storage

# Backend with Memory cd backend # Set environment and run $env:USE_MEMORY_STORE="true"; go run main.go # Frontend (same as above) cd ../frontend npm run dev

Visit: http://localhost:5173

Backend Environment Variables:

# Required ENVIRONMENT=production|development PORT=8080 JWT_SECRET=your-secret-key # Storage Selection USE_MEMORY_STORE=true|false # Redis (if USE_MEMORY_STORE=false) REDIS_URL=redis://user:pass@host:port REDIS_ADDR=localhost:6379 # for development # CORS ALLOWED_ORIGINS=https://your-frontend-domain.com

Frontend Environment Variables:

VITE_ENVIRONMENT=production|development VITE_API_URL=https://your-backend-domain.com

1. Connect GitHub repo to Render
2. Render auto-detects render.yaml
3. Free Tier: Uses in-memory storage (USE_MEMORY_STORE=true)
4. Paid Tier: Add Redis service and set USE_MEMORY_STORE=false

1. Connect GitHub repo to Vercel
2. Set root directory to frontend
3. Environment variables set automatically via vercel.json

1. Register/Login to save your scores
2. Start Game - Click to begin drawing cards
3. Card Types:
   • 😸 Cat Cards - Safe, go to inventory
   • 🛡️ Defuse Cards - Protect against bombs
   • ⏭️ Skip Cards - Safe, just removed
   • 🔄 Shuffle Cards - Reshuffle the deck
   • 💥 Bomb Cards - Game over unless you have defuse
4. Win Condition - Draw all cards without exploding
5. Scoring - Each win increases your score

├── render.yaml # Render deployment config ├── docker-compose.yml # Redis for local development ├── LICENSE # MIT License ├── backend/ # Go API server │ ├── config/ # Environment configuration │ ├── handlers/ # HTTP request handlers │ ├── middleware/ # Auth, CORS, rate limiting │ ├── services/ # Business logic & storage │ │ ├── storageService.go # Storage abstraction │ │ ├── redisStorage.go # Redis implementation │ │ ├── memoryStorage.go # Memory implementation │ │ └── authService.go # Authentication logic │ ├── models/ # Data models │ ├── main.go # Application entry point │ ├── go.mod # Go dependencies │ └── .env.example # Environment template ├── frontend/ # React application │ ├── src/ │ │ ├── components/ # React components │ │ ├── config/ # Environment config │ │ └── state/ # Redux store │ ├── vercel.json # Vercel deployment │ ├── package.json # Node dependencies │ └── .env.example # Environment template 

• users - Complete user profiles (ID, username, email, password hash, scores)
• usernames - Username to user ID mapping for fast lookup
• scores - Username to score mapping for leaderboard

• Same structure as Redis but stored in application memory
• Data resets when server restarts (every ~15 minutes of inactivity on free tier)

• POST /api/auth/register - User registration
• POST /api/auth/login - User login
• GET /api/auth/profile - Get user profile (requires auth)
• POST /api/game/user - Update user score
• GET /api/game/user/:username - Get user score
• GET /api/game/leaderboard - Get game leaderboard

cd backend docker-compose up -d redis $env:USE_MEMORY_STORE="false"; go run main.go # Check logs: "Using Redis storage"

cd backend $env:USE_MEMORY_STORE="true"; go run main.go # Check logs: "Using in-memory storage"

• JWT Authentication - Secure token-based auth
• Password Hashing - bcrypt with salt rounds
• CORS Protection - Configured for specific domains
• Rate Limiting - Prevents API abuse
• Environment Secrets - No hardcoded credentials

• Redis: Sub-millisecond data access, persistent storage
• Memory: Nanosecond access, no network overhead
• Frontend: Optimized bundle, lazy loading, responsive design
• Backend: Efficient Go runtime, minimal dependencies

MIT License - see LICENSE file for details

1. Fork the repository
2. Create your feature branch (git checkout -b feature/amazing-feature)
3. Commit your changes (git commit -m 'Add some amazing feature')
4. Push to the branch (git push origin feature/amazing-feature)
5. Open a Pull Request