Open-source project
Yin-Hongwei/music-website avatar
Yin-Hongwei/music-website

Yin-Hongwei/music-website: a Vue 3 and Spring Boot music site that needs a separate media download and four running processes

A music website built with Vue, Spring Boot and MyBatis.

6,776 stars1,631 forksVueNOASSERTION

At a glance

What is it?
music-website is a learning project with a Vue 3 client, a Vue 3 admin panel and a Spring Boot, MyBatis and MySQL backend. It cannot play anything until you fetch songs from a netdisk, import a SQL file and start Redis, and the author rules out commercial use.
Who is it for?
Use music-website as a study project for a Vue 3 frontend paired with Spring Boot, MyBatis, MySQL and Redis, where the author welcomes learning and exchange. Do not use it as the base of a commercial product: the author refuses commercial use and the repository carries no license identifier.
Can I use it commercially?
Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
Is it still maintained?
Yes. The repository last received commits 12 days ago.
What is it written in?
Mainly Vue, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • Yin-Hongwei/music-website6,776 ★ · +11
Star history
Repository2026-09-232026-11-15
Yin-Hongwei/music-website6.8k6.8k

11 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The songs and images are not in the repository, so a fresh clone plays nothing

The clone step is two commands.

bash
git clone [email protected]:Yin-Hongwei/music-website.git
cd music-website

After that you still need media. The author hosts the songs and images on a Quark netdisk share, protected by an extraction code, and the share link and code are given in the project page. The downloaded data folder goes inside music-server, which yields music-server/data/img/ and music-server/data/song/. Local logs are written to music-server/data/logs/ by default.

The consequence is that the project depends on a third-party file host for its content. If you cannot open that share, you have the code and a database schema but no audio files to point at. The git clone URL also uses SSH, so you need a GitHub SSH key configured before the first command works.

Four processes have to be running before the player does anything

Services are started in a set order, usually in separate terminals. The backend API runs from music-server, Redis runs as redis-server, and the two Vue applications, music-client and music-manage, each use the same pair of commands.

bash
npm install && npm run serve

The backend command differs by platform. The Maven Wrapper bundled with the project is the recommended route on both, and a machine with Maven already installed has a third option.

bash
# macOS / Linux(推荐,使用项目自带 Maven Wrapper)
./mvnw clean spring-boot:run

# Windows(推荐)
mvnw.cmd clean spring-boot:run

# 备选:本机已安装 Maven 时
mvn clean spring-boot:run

Redis is a hard requirement rather than an option, because it appears in the technology stack beside MySQL. If you start the client and admin first and forget Redis or the backend, the pages load but their API calls have nothing to answer them.

Database setup is a manual SQL import plus an edited properties file

There is no migration tool in the quick start. You create a database in MySQL and import sql/yin_music.sql by hand. Then you open music-server/src/main/resources/application-dev.properties and change spring.datasource.username and spring.datasource.password to match your own MySQL account. The dev profile is the default active one, set in application.properties, so those credentials are the ones the backend will read unless you change the profile.

This means the database password lives in a file inside the repository tree. If you commit your local edit, your credentials go with it. The required versions are listed too: JDK 8 or newer, MySQL 8.0 or newer, Redis 5.0.8 or newer, and Node.js 16 or newer, with IntelliJ IDEA or VS Code as the suggested editors.

Two known playback failures both come down to file paths and file integrity

The project lists two troubleshooting cases. When images or music fail to load, confirm that the resources sit in music-server/data/img and music-server/data/song, and start the backend from inside the music-server directory. The second case is that music will not play, and the stated cause is that a resource file may be damaged, in which case you download it again from the netdisk and replace it.

The first case shows that the media location is resolved relative to the directory the backend is started from. Launching the Maven Wrapper from the repository root instead of music-server is therefore a mistake that produces broken images and silent audio even when the data folder is in the right place. The second case means a partial netdisk download can look like an application bug.

Docker Compose builds three images and bakes the API address into the frontend

For a Linux server there is a Docker route, and local development can skip it. Each application carries its own Dockerfile in music-server, music-client and music-manage, while deploy/docker-compose.yml only orchestrates them.

bash
cd deploy
docker compose up --build

After it starts, the client is on http://localhost:8080, the admin panel on http://localhost:8081 and the API on http://localhost:8888. Two optional environment variables exist: MYSQL_ROOT_PASSWORD, and API_PUBLIC_URL, which is the backend address written into the frontend at build time and defaults to http://localhost:8888. Since the address is fixed during the build, pointing the frontend at a different server later means rebuilding the images, not editing a runtime setting. A deployment behind a real hostname has to set API_PUBLIC_URL before the first build.

The feature list covers a client and an admin side, split across two Vue apps

The client side has registration and login, profile editing and a personal center, recommended playlists, playlist and singer display, search across songs and playlists, comments on playlists and songs, and favorites. The player supports play, pause, dragging the progress bar, volume control, lyric sync and download. The admin panel manages banners, users, songs, singers, playlists and comments.

The frontend stack is Vue 3 with TypeScript, Vue Router, Pinia and Axios. The client uses Element Plus and the admin panel uses Naive UI, so the two apps do not share a component library. Anyone planning to restyle both has to learn two sets of components. The backend side is Spring Boot, MyBatis, Redis and local media storage under music-server/data.

Copyright, commercial use and version selection

The project page opens with a statement that the project is shared as technical sharing and is not paid, that the copyright belongs to the author alone, that learning and exchange are welcome at any time, and that commercial use is refused. The repository's license field reports NOASSERTION, so there is no standard license identifier to rely on. Read the LICENSE file in the repository before reusing any part of it, and treat the author's statement as binding on commercial work.

The repository has no GitHub releases; pin a specific Git commit rather than tracking the master branch for a reproducible source snapshot. The last push was 2026-10-20 and the repository is not archived. The implementation approach is explained in a blog post that the project links, which is the place to go for design reasoning behind the code.

Editorial conclusion

Use music-website as a study project for a Vue 3 frontend paired with Spring Boot, MyBatis, MySQL and Redis, where the author welcomes learning and exchange. Do not use it as the base of a commercial product: the author refuses commercial use and the repository carries no license identifier. Before running it, make sure you can reach the netdisk download for the song and image files.

Frequently asked questions

How to set up a music website with Yin-Hongwei/music-website?

Clone the repository, download the media data folder into music-server, import sql/yin_music.sql into MySQL, edit the datasource username and password in application-dev.properties, then start the backend, Redis and the two Vue apps.

What is the music-website project?

It is a full-stack music website for learning, with a Vue 3 client, a Vue 3 admin panel, and a Spring Boot and MyBatis backend on MySQL and Redis. The author does not allow commercial use.

How to play music in the music-website project?

Place the downloaded songs in music-server/data/song and images in music-server/data/img, start the backend from the music-server directory, and open the client. The player offers play, pause, seeking, volume, lyric sync and download.

Official sources

  1. Issues
  2. README
  3. Yin-Hongwei/music-website on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/yin-hongwei-music-website.svg)](https://hysenlabs.com/projects/yin-hongwei-music-website)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/yin-hongwei-music-website.svg)](https://hysenlabs.com/projects/yin-hongwei-music-website)

Was this useful?