msgbyte / msgbyte/tailchat

编译成功但是访问报404 || The compilation was successful but the access reported 404

Open
#299 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
3.6k
Forks
398
Avg merge
1h 14m
Merged PRs (30d)
2

Description

Image cli和Docker Compose都试过了,编译也没出现任何问题,甚至换了两台服务器但是都404
Image I have tried both cli and Docker Compose, and there are no problems with compilation. I even changed two servers but both got 404.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the reported 404 using both the CLI and Docker Compose, checking the compiled deployment's access path and server response. Done means a fresh deployment on a server can be reached without returning 404; the issue does not identify a source file or test to run.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker-compose, typescript
Domain
devops, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.