Quick Start - huanfenz/BookManager2

Source Files

This page is generated from the following source files:

This project is a full-stack Book Management System built with a separated frontend and backend architecture. The backend is implemented using Java with Spring Boot, MyBatis, and MySQL, while the frontend utilizes Vue.js, Axios, and Element UI. The system is designed to be simple to deploy and suitable for beginners learning full-stack development readme.md:5-13.

Environment Requirements

The following environment and tools are required to run this project:

Component	Version	Description
Java	JDK 1.8.0	Required for Spring Boot backend
IDE	IntelliJ IDEA 2021.2.1+	Recommended development environment
Build Tool	Maven 3.3.9	Project build and dependency management
Web Server	SpringBoot embedded Tomcat	No external server required
Database	MySQL 5.7	Data persistence layer

These specifications are documented in the project's environment introduction section readme.md:17-26.

Prerequisites Checklist:

JDK 1.8 installed and JAVA_HOME environment variable configured
MySQL 5.7 service running and accessible
Maven installed (or use the included Maven wrapper)
Git for cloning the repository

Installation Steps

Step 1: Clone the Repository

Clone the backend repository from GitHub:

bash
1git clone https://github.com/huanfenz/BookManager2.git
2cd BookManager2

The corresponding frontend program is available at: https://github.com/huanfenz/BookManagerVue readme.md:15.

Step 2: Database Initialization

Create a new MySQL database and import the schema:

sql
1CREATE DATABASE book_manager;

Import the SQL file located at the project root:

bash
1mysql -u root -p book_manager < book_manager.sql

According to the setup instructions, create a database named book_manager and import the book_manager.sql file readme.md:29-31.

The SQL file contains the complete database schema including core tables such as book_info, book_type, borrow, and user-related tables. The book_info table structure includes fields for book ID, name, author, price, type, description, borrow status, and image URL book_manager.sql:17-36.

Step 3: Configure Database Connection

Open the configuration file at src/main/resources/application.properties and modify the database and Redis settings according to the local environment readme.md:32-34.

The SQL file header indicates the source database was configured with:

Source Host: localhost:3306
Source Schema: book_manager
Server Version: MySQL 5.7.35 book_manager.sql:1-15.

Note: The exact configuration keys and values in application.properties require confirmation by examining the actual file content, as the source file provided appears to be empty or truncated.

Quick Start Path

The recommended minimal path to run the project:

bash
1# 1. Ensure MySQL is running with book_manager database imported
2# 2. Configure database connection in application.properties
3# 3. Build and run using Maven
4mvn spring-boot:run

Alternatively, if using an IDE like IntelliJ IDEA:

Open the project directly in the IDE
Wait for Maven to resolve dependencies
Run the main application class BookManagerApplication

The project setup is described as straightforward with a simple deployment process readme.md:13.

Running and Verification

Starting the Application

After completing the configuration, run the project. The specific startup command or IDE run configuration depends on the development environment readme.md:35.

Accessing the Application

A demo deployment was previously available at:

URL: http://47.97.104.230:8092/BookManager/ readme.md:52

Note: The demo has been disabled to conserve server resources readme.md:50. For local deployment verification, access the application through the configured local server address (typically http://localhost:8080 or the port configured in application.properties).

Test Accounts

The following test accounts are available for verification:

Role	Username	Password
Administrator	admin	admin
Reader	wangpeng	123456

These credentials are documented in the project readme for testing purposes readme.md:54-56.

UI Verification

The project includes screenshots demonstrating the user interface, which can be used to verify successful deployment. The screenshots show the book management interface with features like book listing, search, and management functions readme.md:37-46.

Common Issues and Troubleshooting

Issue 1: Database Connection Failure

Symptoms: Application fails to start with database connection errors.

Possible Causes:

MySQL service not running
Incorrect database credentials in application.properties
Database book_manager not created or SQL file not imported

Solutions:

Verify MySQL service is running: mysqladmin -u root -p status
Check database exists: SHOW DATABASES LIKE 'book_manager';
Verify configuration matches local MySQL settings (host, port, username, password)
Re-import the SQL file if tables are missing

Issue 2: Port Conflict

Symptoms: Application fails to start with "port already in use" error.

Possible Causes:

Another application using the default Tomcat port (typically 8080)
Previous instance of the application still running

Solutions:

Check for running Java processes: jps or ps aux | grep java
Kill any conflicting processes or change the server port in application.properties:
```
properties
1server.port=8092
```

Note: The exact configuration key requires confirmation from the actual application.properties file content.

Issue 3: Redis Connection Error

Symptoms: Application fails to start or runtime errors related to Redis.

Possible Causes:

Redis service not running
Redis configuration not properly set in application.properties

Solutions:

Install and start Redis if required by the application
Verify Redis connection settings in the configuration file

The readme mentions modifying Redis configuration as part of the setup process readme.md:33, indicating Redis is a required dependency.

Issue 4: Maven Dependency Resolution Failure

Symptoms: Build fails with dependency download errors.

Possible Causes:

Network connectivity issues
Maven repository configuration problems
Missing or corrupted local Maven cache

Solutions:

Check network connectivity
Clear Maven cache: rm -rf ~/.m2/repository
Use the included Maven wrapper: ./mvnw spring-boot:run
Verify pom.xml is present and valid

Next Steps

After successfully running the project, consider exploring:

Frontend Integration: Clone and set up the frontend project from https://github.com/huanfenz/BookManagerVue to enable the complete user interface readme.md:15.
API Documentation: Examine the controller classes to understand the available REST API endpoints for book management, user authentication, and borrowing operations.
Database Schema: Review the complete database structure in book_manager.sql to understand the data model, including tables for books, book types, users, and borrow records book_manager.sql:17-157.
Feature Customization: The project is described as suitable for beginners with clear code structure, making it ideal for learning and extending with new features readme.md:13.
Deployment: For production deployment, consider configuring proper database connection pooling, security settings, and externalizing configuration for different environments.