tourze/device-bundle

设备管理和登录日志追踪的 Symfony Bundle

0.1.4 2025-06-01 17:00 UTC

Requires

• php: ^8.1
• doctrine/collections: ^2.3
• doctrine/data-fixtures: ^2.0
• doctrine/dbal: ^4.0
• doctrine/doctrine-bundle: ^2.13
• doctrine/doctrine-fixtures-bundle: ^4.0
• doctrine/orm: ^3.0
• doctrine/persistence: ^3.1 || ^4
• easycorp/easyadmin-bundle: ^4
• knplabs/knp-menu: ^3.7
• symfony/config: ^6.4
• symfony/dependency-injection: ^6.4
• symfony/doctrine-bridge: ^6.4
• symfony/form: ^6.4
• symfony/framework-bundle: ^6.4
• symfony/http-kernel: ^6.4
• symfony/routing: ^6.4
• symfony/security-core: ^6.4
• symfony/yaml: ^6.4 || ^7.1
• tourze/bundle-dependency: 0.0.*
• tourze/doctrine-indexed-bundle: 0.0.*
• tourze/doctrine-snowflake-bundle: 0.1.*
• tourze/doctrine-timestamp-bundle: 0.0.*
• tourze/doctrine-track-bundle: 0.1.*
• tourze/easy-admin-attribute: 0.1.*
• tourze/easy-admin-menu-bundle: 0.1.*
• tourze/operation-system-enum: 0.0.*
• tourze/symfony-routing-auto-loader-bundle: 0.0.*
• tourze/symfony-schedule-entity-clean-bundle: 0.1.*

Requires (Dev)

• phpstan/phpstan: ^2.1
• phpunit/phpunit: ^10.0

MIT

README

English | 中文

A Symfony bundle for managing user devices and login logs with comprehensive tracking capabilities.

Table of Contents

• Features
• Requirements
• Installation
• Configuration
• Quick Start
• Usage
• Advanced Usage
• Database Schema
• Security
• Contributing
• License

Features

• Device Management: Register and manage user devices with unique codes
• User-Device Association: Many-to-many relationship between users and devices
• Login Tracking: Detailed login logs with IP, platform, device info
• Admin Interface: Built-in EasyAdmin controllers for device management
• Data Fixtures: Pre-configured test data for development
• Automatic Cleanup: Scheduled cleanup of old login logs
• Platform Detection: Support for various platforms (iOS, Android, etc.)

Requirements

• PHP 8.1 or higher
• Symfony 7.3 or higher
• Doctrine ORM 3.0+
• EasyAdmin Bundle 4.x

Installation

composer require tourze/device-bundle

Note: If you're working in this monorepo environment, the bundle is automatically available. For Symfony Flex projects, the bundle will be automatically registered in config/bundles.php.

Configuration

The bundle provides optional configuration for customizing behavior:

# config/packages/device.yaml
device:
    # Optional: Configure login log cleanup
    cleanup:
        enabled: true
        retention_days: 30
    
    # Optional: Admin interface settings
    admin:
        enabled: true
        menu_section: "Device Management"

Quick Start

1. Register a Device

<?php

use DeviceBundle\Service\DeviceService;
use DeviceBundle\Entity\Device;

class YourController
{
    public function __construct(
        private DeviceService $deviceService
    ) {}
    
    public function registerDevice(): Device
    {
        return $this->deviceService->register(
            model: 'iPhone 15 Pro',
            code: 'ABC123DEF456'
        );
    }
}

2. Track Login Events

<?php

use DeviceBundle\Service\LoginLogService;
use DeviceBundle\Entity\LoginLog;

class AuthController
{
    public function __construct(
        private LoginLogService $loginLogService
    ) {}
    
    public function logUserLogin(User $user, Request $request): LoginLog
    {
        return $this->loginLogService->logLogin(
            user: $user,
            loginIp: $request->getClientIp(),
            loginPlatform: 'web',
            additionalData: [
                'user_agent' => $request->headers->get('User-Agent'),
                'system_version' => 'Web Browser',
            ]
        );
    }
}

Usage

Device Service

The DeviceService provides methods for device management:

<?php

use DeviceBundle\Service\DeviceService;

$deviceService = $container->get(DeviceService::class);

// Register new device (or get existing)
$device = $deviceService->register('iPhone 15', 'UNIQUE_CODE');

// Find device by code
$device = $deviceService->findByCode('UNIQUE_CODE');

// Get all devices for a user
$devices = $deviceService->getDevicesForUser($user);

Login Log Service

Track user login activities:

<?php

use DeviceBundle\Service\LoginLogService;
use DeviceBundle\Enum\Platform;

$logService = $container->get(LoginLogService::class);

// Log a login event
$loginLog = $logService->logLogin(
    user: $user,
    loginIp: '192.168.1.100',
    loginPlatform: Platform::IOS->value,
    additionalData: [
        'login_imei' => 'DEVICE_IMEI',
        'system_version' => 'iOS 17.0',
        'version' => '1.0.0',
        'device_model' => 'iPhone 15 Pro',
        'net_type' => 'wifi'
    ]
);

// Get recent logins for user
$recentLogins = $logService->getRecentLoginsForUser($user, limit: 10);

Device Status Management

Monitor and update device online status:

<?php

use DeviceBundle\Service\DeviceStatusManager;

$statusManager = $container->get(DeviceStatusManager::class);

// Update device online status
$statusManager->updateOnlineStatus($device, isOnline: true);

// Update last connection info
$statusManager->updateLastConnection($device, ip: '192.168.1.100');

// Get online devices
$onlineDevices = $statusManager->getOnlineDevices();

// Check for timeout devices (offline for > 5 minutes)
$statusManager->checkAndUpdateTimeoutDevices(timeoutSeconds: 300);

Advanced Usage

Custom Device Types

You can extend the device type system:

<?php

use DeviceBundle\Enum\DeviceType;

// The bundle supports various device types
$device->setDeviceType(DeviceType::PHONE);
$device->setDeviceType(DeviceType::TABLET);
$device->setDeviceType(DeviceType::DESKTOP);

Hardware Information Tracking

Update device hardware details:

<?php

use DeviceBundle\Service\DeviceStatusManager;

$statusManager->updateHardwareInfo($device, [
    'deviceType' => 'phone',
    'osVersion' => 'Android 14',
    'brand' => 'Samsung',
    'cpuCores' => 8,
    'memorySize' => '8192',  // MB
    'storageSize' => '256000',  // MB
    'fingerprint' => 'hardware_fingerprint'
]);

Custom Data Fixtures

Create your own device fixtures:

<?php

namespace App\DataFixtures;

use DeviceBundle\DataFixtures\DeviceFixtures;
use Doctrine\Bundle\FixturesBundle\Fixture;
use Doctrine\Common\DataFixtures\DependentFixtureInterface;
use Doctrine\Persistence\ObjectManager;

class AppDeviceFixtures extends Fixture implements DependentFixtureInterface
{
    public function load(ObjectManager $manager): void
    {
        // Use predefined devices
        $device1 = $this->getReference(DeviceFixtures::DEVICE_REFERENCE_1);
        
        // Create custom associations
        // ... your custom logic
    }
    
    public function getDependencies(): array
    {
        return [DeviceFixtures::class];
    }
}

Admin Interface Customization

The bundle provides admin controllers that can be customized:

<?php

// Admin controllers are automatically registered
// - DeviceBundle\Controller\Admin\DeviceCrudController
// - DeviceBundle\Controller\Admin\LoginLogCrudController

// Customize in your dashboard:
use DeviceBundle\Controller\Admin\DeviceCrudController;

public function configureMenuItems(): iterable
{
    // ... other menu items
    
    yield MenuItem::linkToCrud('Devices', 'fas fa-mobile-alt', Device::class);
    yield MenuItem::linkToCrud('Login Logs', 'fas fa-history', LoginLog::class);
}

Data Fixtures

Load test data for development:

# Load all fixtures
php bin/console doctrine:fixtures:load

# Load only device fixtures
php bin/console doctrine:fixtures:load --group=device

# Append without truncating
php bin/console doctrine:fixtures:load --append

Database Schema

Device Table (ims_device)

• id - Snowflake ID
• code - Unique device identifier
• model - Device model name
• name - Device display name
• valid - Device validity status
• reg_ip - Registration IP address
• create_time / update_time - Timestamps

Login Log Table (device_login_log)

• id - Auto-increment ID
• user_id - Associated user
• login_ip - Login IP address
• login_platform - Platform enum
• login_imei - Device IMEI
• login_channel - Login channel
• system_version - OS version
• version - App version
• ip_city - IP location city
• ip_location - Full IP location
• device_model - Device model
• net_type - Network type
• create_time - Log timestamp

Security

Data Privacy

• IP Address Logging: Login IPs are stored for security tracking. Consider GDPR compliance for EU users.
• Device Fingerprinting: Hardware fingerprints are stored as TEXT fields with length validation.
• Automatic Cleanup: Old login logs are automatically cleaned up according to configured retention periods.

Input Validation

• All entity properties include proper validation constraints
• Device codes must be unique and are validated for length
• IP addresses are validated using Symfony's IP constraint
• Device models use regex validation to prevent malicious input

Access Control

• Admin controllers should be protected by proper authentication
• Consider implementing role-based access for device management
• Use CSRF protection on admin forms

Contributing

Please see CONTRIBUTING.md for details.

License

The MIT License (MIT). Please see License File for more information.