mirror of
https://github.com/MHSanaei/3x-ui.git
synced 2026-09-06 18:27:14 +00:00
Kuzz007
ea00e69d4d
Never used by this fork's own distribution (install.sh/x-ui.sh is the only supported install path), AmneziaWG structurally can't run in the Alpine-based image anyway, and Docker Hub publishing was failing on every release for lack of configured credentials. Removed Dockerfile, docker-compose.yml, DockerEntrypoint.sh, DockerInit.sh, .dockerignore, and the docker.yml CI workflow; dropped the now-dead "Docker" README subsection (all 7 languages), the "Docker image"/"Docker Compose" options from the issue/PR templates, and corrected claude-bot.yml's now-stale references to the deleted files, the never-actually-ours ghcr.io/mhsanaei/3x-ui image, and (caught in passing) an already-stale claim that Windows is a supported platform. Left untouched: generic container-runtime adaptations that apply regardless of image source (x-ui.sh's running-in-docker detection, the virtual-interface-name filters, the DNS-over-container-network note) and deploy/test/smoke-noninteractive.sh, which uses Docker only as its own test sandbox, not as something this repo ships. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
63 lines
1.7 KiB
Markdown
63 lines
1.7 KiB
Markdown
## Summary
|
|
|
|
<!-- What does this PR do? One or two sentences. -->
|
|
|
|
## Why
|
|
|
|
<!--
|
|
What problem does this solve, or what use case does it enable?
|
|
Link related issues here: "Closes #123", "Refs #456".
|
|
-->
|
|
|
|
## Type of change
|
|
|
|
- [ ] Bug fix
|
|
- [ ] New feature
|
|
- [ ] Refactoring (no behavior change)
|
|
- [ ] Documentation
|
|
- [ ] Tests only
|
|
- [ ] Build / CI / tooling
|
|
- [ ] Other
|
|
|
|
## Areas affected
|
|
|
|
- [ ] Frontend (UI / panel pages)
|
|
- [ ] Backend (API endpoints, login, settings)
|
|
- [ ] Xray config generation
|
|
- [ ] Subscription (share links / Clash / JSON)
|
|
- [ ] Statistics / traffic counters
|
|
- [ ] Database / migrations
|
|
- [ ] Install / upgrade script
|
|
- [ ] Multi-node (sub-nodes)
|
|
- [ ] Telegram bot
|
|
|
|
## How was this tested?
|
|
|
|
<!--
|
|
Concrete steps the reviewer can repeat. For UI changes: which page,
|
|
which actions, which browser. For backend: which endpoint, which payload,
|
|
which response. Mention any new unit/integration tests added.
|
|
-->
|
|
|
|
## Screenshots / recordings
|
|
|
|
<!-- Required for UI changes. Drag images or GIFs here. Remove if N/A. -->
|
|
|
|
## Breaking changes
|
|
|
|
<!--
|
|
Does this change require existing users to update their config, run a
|
|
migration, or change their API calls? If yes, describe the migration path.
|
|
Write "None" if there are no breaking changes.
|
|
-->
|
|
|
|
## Checklist
|
|
|
|
- [ ] I tested the change locally and confirmed the described behavior.
|
|
- [ ] I added or updated tests for the new behavior (when applicable).
|
|
- [ ] `go build ./...` and the test suite pass locally.
|
|
- [ ] For frontend changes: `npm run lint`, `npm run typecheck`, and `npm run build` pass.
|
|
- [ ] I updated the Wiki / README / API docs if user-facing behavior changed.
|
|
- [ ] My commits follow the project's existing message style.
|
|
- [ ] I have no unrelated changes mixed into this PR.
|