MyGo 云音乐
用 Go 与 MyGo 写成的第三方网易云音乐桌面客户端。原生界面,没有 WebView;边下边播,无损与 Hi-Res,逐字歌词与「律动」,刘海播放器。
Translation pending
Music for Business
Translation pending
MediaTypeScript · MDXGitHub @AlvinBrockeOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Background music for businesses. Curated daytime and evening playlists, a weekly schedule that plays them automatically, and in-store announcements. Built with Next.js, Convex and Clerk.
Taken from the repository README
Loading the full README.
Read the full README ↗Curated ambient music for hospitality venues. A web app that lets venue operators stream atmosphere-matched audio channels, build playlists, and schedule automatic atmosphere changes throughout the day.
| Layer | Technology |
|---|---|
| Framework | Next.js 16 (App Router) |
| Auth | Clerk |
| Database | Convex |
| Client state | Zustand |
| Styling | Tailwind CSS |
| Deployment | Vercel |
| Testing | Vitest + convex-test |
src/
app/
(auth)/ — sign-in, sign-up, onboarding routes
(main)/ — protected app routes (dashboard, settings, etc.)
home/ — public marketing page (/home)
components/
landing/ — marketing page sections
layout/ — sidebar, top bar, player bar
ui/ — shared UI primitives
store/ — Zustand player store
proxy.ts — Clerk auth middleware (not middleware.ts)
convex/ — database schema, queries, and mutations
schema.ts — table definitions
channels.ts — curated music stream CRUD
tracks.ts — individual track CRUD
playlists.ts — user playlist CRUD + track management
scheduleBlocks.ts — timed atmosphere scheduling
userProfiles.ts — user preferences and plan
Prerequisites: Node.js 22+, pnpm
pnpm install
Copy the environment template and fill in your keys (see Environment variables):
cp .env.local.example .env.local
Start the Convex dev server (push schema + functions):
CONVEX_AGENT_MODE=anonymous npx convex dev --once
Start the Next.js dev server:
pnpm dev # http://localhost:3000
Run
npx convex dev --onceagain after any change toconvex/files.
Required in .env.local:
CLERK_SECRET_KEY=
NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY=
NEXT_PUBLIC_CLERK_SIGN_IN_URL=/signin
NEXT_PUBLIC_CLERK_SIGN_UP_URL=/signup
NEXT_PUBLIC_CLERK_SIGN_IN_FALLBACK_REDIRECT_URL=/dashboard
NEXT_PUBLIC_CLERK_SIGN_UP_FALLBACK_REDIRECT_URL=/dashboard
CONVEX_DEPLOYMENT=
NEXT_PUBLIC_CONVEX_URL=
NEXT_PUBLIC_CONVEX_SITE_URL=
npx convex dev --once (e.g. http://127.0.0.1:3210 locally, https://<deployment>.convex.cloud in production)Convex tables:
| Table | Description |
|---|---|
channels | Curated music streams with BPM, category, and audio URL |
tracks | Individual tracks with energy level, duration, and channel assignment |
playlists | User-created playlists (public or private) |
playlistTracks | Join table linking tracks to playlists with ordering |
scheduleBlocks | Timed blocks that automate channel switching throughout the day |
userProfiles | User preferences, plan tier, and onboarding state |
Seed the database with sample channels and tracks:
npx convex run channels:seed --prod
npx convex run tracks:seed --prod
pnpm test # utils + Zustand store (jsdom, 15 tests)
pnpm test:watch # same, watch mode
pnpm test:convex # Convex function tests (in-memory, 33 tests)
All 48 tests run fully offline — no real Convex deployment is touched.
pnpm build
Run this before opening a pull request.
GitHub Actions runs on every push and pull request to main:
tsc --noEmit then next build (only runs if tests pass)Deployment is handled by Vercel's own Git integration, not by GitHub Actions: pushes to main deploy to production and pull requests get a preview deployment, both reported back as the Vercel check.
Required GitHub secrets (used by the build job): NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY, CLERK_SECRET_KEY, NEXT_PUBLIC_CONVEX_URL.
src/proxy.ts (Next.js 16 convention in this project — do not rename to middleware.ts)/dashboard, /account, /explore, /schedule, /playlists, /library, /settings/signinmain: feat/my-featurefeat:, fix:, refactor:, chore: