ELADMIN Administration Management System

The project is organized into functional modules to facilitate maintenance and extension:

Backend Modules

• eladmin-common: Contains public utilities, common configurations (Web, Redis, Redisson, Async Thread Pools), custom annotations, aspects, base Entity/DTO classes, and unified exception handling.
• eladmin-system: The core module and the application entry point. It contains the sysrunner (for data processing on startup) and various system modules like login authorization, monitoring, and task scheduling.
• eladmin-logging: A dedicated module for system logging. Other modules should include this to record logs.
• eladmin-tools: Third-party integration tools including Email, Amazon S3 compatible storage, Alipay, and Local Storage.
• eladmin-generator: The code generation engine used to produce CRUD code for both front-end and back-end.

You can test the system functionality via the official demo site.

• Demo URL: https://eladmin.vip/demo
• Default Credentials:
  • Username: admin
  • Password: 123456

admin / 123456

The eladmin-common module provides several utility classes used throughout the system:

The App class is a JPA entity representing an application within the maintenance module. It maps to the mnt_app database table and extends BaseEntity to include standard audit fields (like creation/update timestamps).

Use this model to manage application-specific deployment metadata, including network ports, file paths for uploads, deployments, and backups, as well as shell scripts for lifecycle management.

@Entity
@Getter
@Setter
@Table(name="mnt_app")
public class App extends BaseEntity implements Serializable {
    @Id
    @Column(name = "app_id")
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    private Long id;

    private String name;
    private int port;
    private String uploadPath;
    private String deployPath;
    private String backupPath;
    private String startScript;
    private String deployScript;
}

The App class provides a copy(App source) method to perform a partial update or clone. It uses BeanUtil.copyProperties with CopyOptions.create().setIgnoreNullValue(true), meaning only non-null fields from the source object will be applied to the current instance. This is useful for updating existing records with data from a DTO while preserving existing values for omitted fields.

// Example: Updating an existing app with new values from a source object
App existingApp = appRepository.findById(1L).orElseThrow();
App updateData = new App();
updateData.setName("New App Name");
// updateData.setPort(0); // This would be ignored because it's null/default if not set

existingApp.copy(updateData);
appRepository.save(existingApp);