😎 The next generation of RESTful API service and more feature for Mix Space, powered by @nestjs.
License: Other
本项目使用 Monorepo 进行管理。
此项目在 apps/ 目录下的所有文件均使用 GNU Affero General Public License v3.0 (AGPLv3) with Additional Terms (ADDITIONAL_TERMS) 许可。
其他部分使用 MIT License 许可。
详情请查看 LICENSE 和 ADDITIONAL_TERMS。
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
![renovate[bot] avatar](https://avatars.githubusercontent.com/in/2740?v=4 "renovate[bot]")
netease 函数在最新的Core没有返回内容
使用的内容是https://github.com/mx-space/snippets/blob/main/kami/functions/netease.ts
本地pnpm dev出现以下内容
api-doc尝试，无返回
song 函数响应正常
Curl netease 函数无返回
在我尝试重新编辑该云函数的时候，出现了此错误
复现使用的系统是ArchLinux
Redis版本为 7.0.2
MongoDB版本为 5.0.9
Node版本 v16.15.1
疑问：
建议：
当前的垃圾评论过滤只有关键词过滤 尚存不足
建议添加以下功能
No response
No response
如题，目前定位的猜测原因是：
客户端访问了前端 Shiro 博文 URL，如 https://arthals.ink/posts/experience/attack-lab 的同时没有和后端沟通，是服务器上的 Next.js 同后端进行的沟通（服务端渲染），即反向代理前端的服务端 2323 端口会请求反向代理后端 API 地址的服务器 2333 端口的 https://api.arthals.ink/api/v2/posts/experience/attack-lab 。这导致后端访问日志中一直只能看到服务器自己的 IP 在请求 API ，也就导致了阅读量的计算不准确。经过尝试，我发现此问题和前后端是否设置 XFF/XRP 头部没有任何关系。
我希望能够直接将阅读量改为按照请求次数计数，这样就能解决这个问题了（否则前端 Shiro 更改渲染模式我估计会更加难以实现）
同时，我注意到，在 mx-admin 页面的数据-访问路径这个列表并不会随着切换页码而刷新，必须切换页码后再次刷新页面才能更新（即使URL参数已经改变至 https://api.arthals.ink/proxy/qaqdmin#/analyze?page=2 ，但是显示的依旧是https://api.arthals.ink/proxy/qaqdmin#/analyze?page=1 的内容）
打开控制台和后台刷新试试即可复现
System:
OS: Linux 5.15 Ubuntu 22.04.3 LTS 22.04.3 LTS (Jammy Jellyfish)
CPU: (2) x64 Intel(R) Xeon(R) Platinum 8255C CPU @ 2.50GHz
Memory: 5.75 GB / 7.25 GB
Container: Yes
Shell: 5.8.1 - /usr/bin/zsh
Binaries:
Node: 18.18.0 - ~/.nvm/versions/node/v18.18.0/bin/node
npm: 10.1.0 - ~/.nvm/versions/node/v18.18.0/bin/npm
pnpm: 8.8.0 - ~/.nvm/versions/node/v18.18.0/bin/pnpmpnpm
使用 docker 部署
无
错误日志
17:56:28 ERROR [AuthService] clerk jwt valid error: invalid algorithm
17:56:28 ERROR [AuthService] clerk jwt valid error: invalid algorithm
17:56:28 WARN [AllExceptionsFilter] IP: 43.207.68.61 错误信息：(401) 身份过期 Path: /api/v2/aggregate/stat?t=1708509376108
17:56:28 ERROR [AuthService] clerk jwt valid error: invalid algorithm
17:56:28 WARN [AllExceptionsFilter] IP: 43.207.68.61 错误信息：(404) Cannot GET /api/v2/init?t=1708509376285 Path: /api/v2/init?t=1708509376285
17:56:33 ERROR [AuthService] clerk jwt valid error: invalid algorithm
17:56:33 WARN [UserService] 主人已登录，IP: 43.207.68.61
17:56:35 ERROR [Catch] Schema hasn't been registered for model "recentlies".
Use mongoose.model(name, schema)
Use mongoose.model(name, schema)
at Connection.model (entrypoints.js:241:4323)
at _getModelFromConn (entrypoints.js:596:1564)
at addModelNamesToMap (entrypoints.js:596:345)
at getModelsMapForPopulate (entrypoints.js:590:11812)
at populate (entrypoints.js:710:581)
at _populate (entrypoints.js:707:7939)
at entrypoints.js:707:7780
at new Promise (<anonymous>)
at Function.populate (entrypoints.js:707:7757)
at le.Query._find (entrypoints.js:783:1016)
[February 21, 2024 at 5:56:35 PM] /api/v2/comments?t=1708509382922&page=1&size=10&state=0: Schema hasn't been registered for model "recentlies".
Use mongoose.model(name, schema)
MissingSchemaError: Schema hasn't been registered for model "recentlies".
Use mongoose.model(name, schema)
at Connection.model (/app/entrypoints.js:241:4323)
at _getModelFromConn (/app/entrypoints.js:596:1564)
at addModelNamesToMap (/app/entrypoints.js:596:345)
at getModelsMapForPopulate (/app/entrypoints.js:590:11812)
at populate (/app/entrypoints.js:710:581)
at _populate (/app/entrypoints.js:707:7939)
at /app/entrypoints.js:707:7780
at new Promise (<anonymous>)
at Function.populate (/app/entrypoints.js:707:7757)
at le.Query._find (/app/entrypoints.js:783:1016)
17:56:41 ERROR [Catch] Schema hasn't been registered for model "recentlies".
Use mongoose.model(name, schema)
Use mongoose.model(name, schema)
at Connection.model (entrypoints.js:241:4323)
at _getModelFromConn (entrypoints.js:596:1564)
at addModelNamesToMap (entrypoints.js:596:345)
at getModelsMapForPopulate (entrypoints.js:590:11812)
at populate (entrypoints.js:710:581)
at _populate (entrypoints.js:707:7939)
at entrypoints.js:707:7780
at new Promise (<anonymous>)
at Function.populate (entrypoints.js:707:7757)
at le.Query._find (entrypoints.js:783:1016)
[February 21, 2024 at 5:56:41 PM] /api/v2/comments?t=1708509388704&page=1&size=10&state=0: Schema hasn't been registered for model "recentlies".
Use mongoose.model(name, schema)
MissingSchemaError: Schema hasn't been registered for model "recentlies".
Use mongoose.model(name, schema)
at Connection.model (/app/entrypoints.js:241:4323)
at _getModelFromConn (/app/entrypoints.js:596:1564)
at addModelNamesToMap (/app/entrypoints.js:596:345)
at getModelsMapForPopulate (/app/entrypoints.js:590:11812)
at populate (/app/entrypoints.js:710:581)
at _populate (/app/entrypoints.js:707:7939)
at /app/entrypoints.js:707:7780
at new Promise (<anonymous>)
at Function.populate (/app/entrypoints.js:707:7757)
at le.Query._find (/app/entrypoints.js:783:1016)紧急事项：我们近期发现部分用户数据库遭到非法入侵。初步调查显示，此次安全事件可能与 Docker 容器中的 MongoDB 端口被公开暴露在互联网上有关。
问题描述：若您的 MongoDB 的端口在 Docker 容器中暴露在公网上，可能会增加被恶意攻击的风险。
解决方案：
docker-compose 文件。如果您的配置与下面的类似： mongo:
container_name: mongo
image: mongo
volumes:
- ./data/db:/data/db
ports:
- '3344:27017'
networks:
- app-network
restart: always
redis:
image: redis
container_name: redis那么您需要重点关注 ports 项。
ports 配置项中的 '3344:27017' 删除，从而防止外部访问。如果您仍然需要端口转发，请确保只在 127.0.0.1 上进行监听，这样可以确保只有本机可以访问，如： ports:
- '127.0.0.1:3344:27017'127.0.0.1 上监听。最后，请定期检查并更新您的系统和服务，以确保其安全性。如果有任何疑问或需要进一步的帮助，请及时联系我们。
cor使用docker部署，最新版本
前端主题是shiro，，最新版本，使用的vercel部署
问题：
markdown文章中的单独参考链接，预览的时候正常，但是发布后部分不显示，我测试的2个链接只显示GitHub网站的链接。
复现：
测试内容
预览界面
网站界面只显示GitHub的链接
怎么感觉似曾相识（？
起因是发现 admin 更新 3.36 了 就重新拉了一下docker镜像，然后又跳出这个问题来了（
no need
no need.pnpm
This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.
These updates have all been created already. Click a checkbox below to force a retry/rebase of any.
docker-compose.yml
innei/mx-server 5
dockerfile
node 20-alpinenode 20-alpine
.github/workflows/api-client.yml
actions/checkout v4actions/setup-node v4actions/cache v4pnpm/action-setup v3.0.0.github/workflows/ci.yml
actions/checkout v4docker/metadata-action v5docker/setup-qemu-action v3docker/setup-buildx-action v3docker/build-push-action v5actions/checkout v4actions/setup-node v4pnpm/action-setup v3.0.0actions/cache v4supercharge/mongodb-github-action v1.10.0supercharge/redis-github-action 1.8.0actions/checkout v4actions/setup-node v4pnpm/action-setup v3.github/workflows/release.yml
actions/checkout v4actions/setup-node v4supercharge/mongodb-github-action v1.10.0supercharge/redis-github-action 1.8.0pnpm/action-setup v3.0.0actions/cache v4actions/create-release v1actions/upload-release-asset v1robinraju/release-downloader v1.10appleboy/scp-action v0.1.7actions/checkout v4docker/metadata-action v5docker/setup-buildx-action v3docker/build-push-action v5docker/login-action v3docker/build-push-action v5ubuntu 22.04
apps/core/external/pino/package.json
apps/core/external/request/package.json
apps/core/package.json
@algolia/client-search ^4.22.1@aws-sdk/client-s3 3.556.0@babel/core 7.24.4@babel/plugin-transform-modules-commonjs 7.24.1@babel/plugin-transform-typescript 7.24.4@babel/types ^7.24.0@clerk/clerk-sdk-node 5.0.2@fastify/cookie 9.3.1@fastify/multipart 8.2.0@fastify/static 7.0.3@innei/next-async 0.3.0@nestjs/cache-manager 2.2.2@nestjs/common 10.3.8@nestjs/core 10.3.8@nestjs/event-emitter 2.0.4@nestjs/mapped-types ^2.0.5@nestjs/platform-fastify 10.3.8@nestjs/platform-socket.io 10.3.8@nestjs/schedule 4.0.2@nestjs/throttler 5.1.2@nestjs/websockets 10.3.8@simplewebauthn/server 9.0.3@socket.io/redis-adapter 8.3.0@socket.io/redis-emitter 5.1.0@typegoose/auto-increment 4.3.0@typegoose/typegoose 12.4.0@types/jsonwebtoken 9.0.6algoliasearch 4.23.3axios ^1.6.7axios-retry 4.1.0bcryptjs ^2.4.3cache-manager 5.5.1cache-manager-ioredis-yet 2.0.3class-validator-jsonschema 3.1.2cls-hooked ^4.2.2commander 12.0.0dayjs 1.11.10ejs 3.1.10form-data 4.0.0get-image-colors 4.0.1image-size 1.1.1inquirer ^9.2.15isbot 5.1.5js-yaml ^4.1.0json5 2.2.3jsonwebtoken 9.0.2jszip 3.10.1linkedom 0.16.11lodash ^4.17.21lru-cache 10.2.1marked 12.0.2mime-types ^2.1.35mkdirp ^3.0.1mongoose 8.3.2mongoose-aggregate-paginate-v2 1.0.7mongoose-autopopulate 1.1.0mongoose-lean-getters 2.0.1mongoose-lean-virtuals 0.9.1mongoose-paginate-v2 1.8.0nestjs-pretty-logger 0.2.2node-machine-id 1.1.12nodemailer 6.9.13openai 4.38.5pluralize ^8.0.0qs 6.12.1reflect-metadata 0.2.2remove-markdown 0.5.0remove-md-codeblock 0.0.4rxjs 7.8.1semver 7.6.0slugify 1.6.6source-map-support ^0.5.21ua-parser-js 1.0.37vm2 3.9.19wildcard-match 5.1.3xss 1.0.15zx-cjs 7.0.7-0@nestjs/cli 10.3.2@nestjs/schematics 10.1.1@nestjs/testing 10.3.8@swc/core 1.5.2@types/babel__core 7.20.5@types/bcryptjs ^2.4.6@types/cache-manager 4.0.6@types/cls-hooked ^4.3.8@types/ejs 3.1.5@types/get-image-colors 4.0.5@types/js-yaml 4.0.9@types/lodash 4.17.0@types/mime-types 2.1.4@types/mongoose-aggregate-paginate-v2 1.0.12@types/node 20.12.7@types/nodemailer 6.4.14@types/qs 6.9.15@types/remove-markdown 0.3.4@types/semver 7.5.8@types/ua-parser-js 0.7.39@types/validator 13.11.9@vercel/ncc 0.38.1cron ^3.1.6husky 9.0.11ioredis 5.4.1socket.io ^4.7.4unplugin-swc 1.4.5vite-tsconfig-paths 4.3.2mongodb-memory-server ^9.1.5redis-memory-server ^0.10.0external/pino/package.json
external/request/package.json
package.json
zx-cjs 7.0.7-0@innei/eslint-config-ts 0.13.1@innei/prettier 0.13.1@types/node 20.12.7cross-env 7.0.3eslint-plugin-unused-imports 3.1.0husky 9.0.11lint-staged 15.2.2prettier 3.2.5rimraf 5.0.5ts-node 10.9.2tsconfig-paths 4.2.0tsup 8.0.2typescript 5.4.5vite-tsconfig-paths 4.3.2mongodb-memory-server 9.1.8redis-memory-server 0.10.0semver 7.6.0typescript 5.4.5pnpm 9.0.6packages/api-client/package.json
@types/cors 2.8.17@types/express 4.17.21@types/lodash 4.17.0abort-controller 3.0.0axios ^1.6.7camelcase-keys ^9.1.3cors 2.8.5express 4.19.2form-data 4.0.0lodash 4.17.21tsup 8.0.2umi-request 1.4.0packages/external/package.json
nanoid 5.0.7packages/webhook/package.json
express 4.19.2
环境：debain11.8
版本：v4.3.12
安装方式为docker-compose
按照教程部署后端，访问反代域名和ip:2333会出现{"ok":0,"message":"Cannot GET /"}
日志为：
�[90m24:02:30�[39m �[32m[Nest] 1 - �[39m10/21/2023, 12:02:30 AM �[32m LOG�[39m �[32m�[34m数据目录已经建好：/root/.mx-space�[39m�[39m
�[90m24:02:30�[39m �[32m[Nest] 1 - �[39m10/21/2023, 12:02:30 AM �[32m LOG�[39m �[32m�[34m临时目录已经建好：/tmp/mx-space�[39m�[39m
�[90m24:02:30�[39m �[32m[Nest] 1 - �[39m10/21/2023, 12:02:30 AM �[32m LOG�[39m �[32m�[34m日志目录已经建好：/root/.mx-space/log�[39m�[39m
�[90m24:02:30�[39m �[32m[Nest] 1 - �[39m10/21/2023, 12:02:30 AM �[32m LOG�[39m �[32m�[34m资源目录已经建好：/root/.mx-space/assets�[39m�[39m
�[90m24:02:30�[39m �[32m[Nest] 1 - �[39m10/21/2023, 12:02:30 AM �[32m LOG�[39m �[32m�[34m文件存放目录已经建好：/root/.mx-space/static�[39m�[39m
�[90m24:02:31�[39m cwd: /app
�[90m24:02:31�[39m �[36mℹ�[39m [�[33mMongoDB�[39m] �[32mconnecting...�[39m
�[90m24:02:31�[39m �[36mℹ�[39m [�[33mMongoDB�[39m] �[32mreadied!�[39m
�[90m24:02:33�[39m �[36mℹ�[39m ENV: production
�[90m24:02:33�[39m �[32m✔�[39m [P1] Server listen on: http://127.0.0.1:2333
�[90m24:02:33�[39m �[32m✔�[39m [P1] Admin Dashboard: http://127.0.0.1:2333/qaqdmin
�[90m24:02:33�[39m �[32m✔�[39m [P1] Admin Local Dashboard: http://127.0.0.1:2333/proxy/qaqdmin
�[90m24:02:33�[39m �[36mℹ�[39m [�[95mSystem�[39m] �[32mServer is up. �[33m+5191ms�[39m�[32m�[39m
�[90m24:02:33�[39m �[43m�[30m WARN �[39m�[49m [�[33mEmailService�[39m] �[33m未启动邮件通知�[39m
�[90m24:02:36�[39m �[43m�[30m WARN �[39m�[49m [�[33mAllExceptionsFilter�[39m] �[33mIP: ***.101.144.50 错误信息：(404) Cannot GET / Path: /�[39m
�[90m24:02:38�[39m �[43m�[30m WARN �[39m�[49m [�[33mAllExceptionsFilter�[39m] �[33mIP: ***.101.144.50 错误信息：(404) Cannot GET / Path: /�[39m
�[90m24:02:57�[39m �[43m�[30m WARN �[39m�[49m [�[33mAllExceptionsFilter�[39m] �[33mIP: ***.101.144.50 错误信息：(404) Cannot GET / Path: /�[39m
�[90m24:02:59�[39m �[43m�[30m WARN �[39m�[49m [�[33mAllExceptionsFilter�[39m] �[33mIP: ***.101.144.50 错误信息：(404) Cannot GET / Path: /�[39m
�[90m24:03:00�[39m �[43m�[30m WARN �[39m�[49m [�[33mAllExceptionsFilter�[39m] �[33mIP: ***.101.144.50 错误信息：(404) Cannot GET / Path: /�[39m
�[90m24:03:02�[39m �[43m�[30m WARN �[39m�[49m [�[33mAllExceptionsFilter�[39m] �[33mIP: ***.101.144.50 错误信息：(404) Cannot GET / Path: /�[39m
�[90m24:05:00�[39m �[36mℹ�[39m [�[33mCronService�[39m] �[32m--> 清理日志文件成功�[39m
clog.timero.xyz
环境：debain11.8
版本：v4.3.12
浏览器：vivaldinpm
我想要在本地的 Apple M2 上部署 mx-sapce 🤪
请提供一个 arm 的 docker image 🫡
No response
跟着文档
无法运行起来，貌似是现在的镜像不支持在 arm 上面运行
环境如图
Windows正常录入密钥
后台报错
2.后台地址无法自定义
系统初始化的时候可以输入后台地址路径，那为啥子没办法改后台地址
3.教程文档内容需修正
我是一个了解mx-space存在但是是没用过的人，照着教程弄了很久第一次打开后端依旧还是提示
{
"ok": 0,
"message": "Cannot GET /"
}
在我翻遍文档无果后Google了一番才发现原来有 /qwqadmin 这一个管理后台的入口，而我在教程文档里没有看到，再三阅览，我发现了这段话
我说你们。。。真的很歧视小白吗？
另外再建议当issue累积到一个程度后可以开一个报错专栏，方便萌新知道是哪出了问题
以上就是所有的内容。
有附图
Linux VM-8-17-centos 3.10.0-1160.99.1.el7.x86_64 #1 SMP Wed Sep 13 14:19:20 UTC 2023 x86_64 x86_64 x86_64 GNU/Linuxn/a
我在一台机器上试图使用docker开启两个mx-space服务，它们两个总会有一个不工作。
主要问题出现在，无论在docker_compose.yml中设置什么名称的redis及mongo，mx-space容器内总是会尝试访问原来名称的redis和mongo服务，但名称以及端口我都已经修改过了。
如以下示例:
正常流程的yml，它是正常工作的:
version: '3.8'
services:
app:
container_name: mx-server
image: innei/mx-server:latest
command: bash ./docker-run.sh
environment:
- TZ=Asia/Shanghai
- NODE_ENV=production
- ALLOWED_ORIGINS
- JWT_SECRET
- ENCRYPT_KEY
- ENCRYPT_ENABLE
volumes:
- ./data/mx-space:/root/.mx-space
ports:
- '127.0.0.1:2333:2333'
depends_on:
- mongo
- redis
links:
- mongo
- redis
networks:
- app-network
restart: always
healthcheck:
test: ['CMD', 'curl', '-f', 'http://127.0.0.1:2333/api/v2/ping']
interval: 1m30s
timeout: 30s
retries: 5
start_period: 30s
mongo:
container_name: mongo
image: mongo
volumes:
- ./data/db:/data/db
networks:
- app-network
restart: always
redis:
image: redis
container_name: redis
networks:
- app-network
restart: always
networks:
app-network:
driver: bridge
修改后的yml:
version: '3.8'
services:
miao-app:
container_name: miao-mx-server
image: innei/mx-server:latest
command: bash ./docker-run.sh
environment:
- TZ=Asia/Shanghai
- NODE_ENV=production
- ALLOWED_ORIGINS
- JWT_SECRET
- ENCRYPT_KEY
- ENCRYPT_ENABLE
volumes:
- ./data/mx-space:/root/.mx-space
ports:
- '127.0.0.1:3332:2333'
depends_on:
- miao-mongo
- miao-redis
links:
- miao-mongo
- miao-redis
networks:
- miao-app-network
restart: always
healthcheck:
test: ['CMD', 'curl', '-f', 'http://127.0.0.1:2333/api/v2/ping']
interval: 1m30s
timeout: 30s
retries: 5
start_period: 30s
miao-mongo:
container_name: miao-mongo
image: mongo
volumes:
- ./data/db:/data/db
networks:
- miao-app-network
restart: always
miao-redis:
image: redis
container_name: miao-redis
networks:
- miao-app-network
restart: always
networks:
miao-app-network:
driver: bridge
它会报错:
[Nest] 1 - 02/18/2024, 12:02:25 PM LOG 数据目录已经建好：/root/.mx-space
[Nest] 1 - 02/18/2024, 12:02:25 PM LOG 临时目录已经建好：/tmp/mx-space
[Nest] 1 - 02/18/2024, 12:02:25 PM LOG 日志目录已经建好：/root/.mx-space/log
[Nest] 1 - 02/18/2024, 12:02:25 PM LOG 资源目录已经建好：/root/.mx-space/assets
[Nest] 1 - 02/18/2024, 12:02:25 PM LOG 文件存放目录已经建好：/root/.mx-space/static
[Nest] 1 - 02/18/2024, 12:02:25 PM LOG 文件回收站目录已经建好：/tmp/mx-space/trash
cwd: /app
ERROR [ioredis] Unhandled error event: Error: getaddrinfo EAI_AGAIN redis
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:107:26)
at GetAddrInfoReqWrap.callbackTrampoline (node:internal/async_hooks:130:17)
ERROR [ioredis] Unhandled error event: Error: getaddrinfo EAI_AGAIN redis
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:107:26)
at GetAddrInfoReqWrap.callbackTrampoline (node:internal/async_hooks:130:17)
ERROR [ioredis] Unhandled error event: Error: getaddrinfo EAI_AGAIN redis
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:107:26)
at GetAddrInfoReqWrap.callbackTrampoline (node:internal/async_hooks:130:17)
ERROR [ioredis] Unhandled error event: Error: getaddrinfo EAI_AGAIN redis
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:107:26)
at GetAddrInfoReqWrap.callbackTrampoline (node:internal/async_hooks:130:17)
ERROR [ioredis] Unhandled error event: Error: getaddrinfo EAI_AGAIN redis
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:107:26)
at GetAddrInfoReqWrap.callbackTrampoline (node:internal/async_hooks:130:17)
ERROR [ioredis] Unhandled error event: Error: getaddrinfo EAI_AGAIN redis
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:107:26)
at GetAddrInfoReqWrap.callbackTrampoline (node:internal/async_hooks:130:17)
above
Linux version 5.15.0-84-generic (buildd@lcy02-amd64-005) (gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #93-Ubuntu SMP Tue Sep 5 17:16:10 UTC 2023
Docker
Client: Docker Engine - Community
Version: 25.0.3更新了 v5.1.2，然后文章管理这成这样了
升级 v5.1.2，然后打开后台文章管理
System：
Need to install the following packages:
[email protected]
Ok to proceed? (y) y
System:
OS: Linux 6.1 Debian GNU/Linux 12 (bookworm) 12 (bookworm)
CPU: (2) x64 Intel(R) Xeon(R) Platinum 8255C CPU @ 2.50GHz
Memory: 824.09 MB / 1.80 GB
Container: Yes
Shell: 5.2.15 - /bin/bash
Binaries:
Node: 18.19.0 - /usr/bin/node
npm: 9.2.0 - /usr/bin/npm
pnpm: 8.15.2 - /usr/local/bin/pnpmAPI：
{"name":"@mx-space/core","author":"Innei <https://innei.ren>","version":"5.1.2","homepage":"https://github.com/mx-space/core#readme","issues":"https://github.com/mx-space/core/issues"}
admin 专用 config 不再归入通用 config 中。
昨天上后台好像显示有新的更新 ---- 面板版本: 3.24.2。
我在后台Output那边更新，但是半小时一直没反应，随后去mix space文档手动更新。
参考的是这篇，安装依赖的时候 pnpm i 也一直未动，执行了后面的构建、启动前端。
最后前台崩了，https://yuano.cc/。显示502 Bad Gateway
请问怎么可以解决恢复一下呀......感谢！！后端显示是完好的。
对了，想起来我是国内的机器，可能拉取拉不到，所以一直更新不动....
Ubuntu/20.04 LTS amd64（64 位）
国内百度云主机。
11:11:44 WARN [AllExceptionsFilter] IP: 错误信息: (404) Cannot GET / Path: /
11:11:45 WARN [AllExceptionsFilter] IP: 错误信息: (404) Cannot GET / Path: /
11:23:23 WARN [AllExceptionsFilter] IP: 错误信息: (404) Cannot GET /api/v2/init?t=Path: /api/v2/init?t=
11:23:25 WARN [UserService] 主人已登录, IP:
11:23:25 WARN [UserService] 主人已登录, IP:
11:24:22 WARN [AllExceptionsFilter] IP:错误信息: (404) Cannot GET / Path: /
11:26:20 WARN [AllExceptionsFilter] IP:错误信息: (404) Cannot GET /api/v2/init?t=Path: /api/v2/init?t=
11:26:22 WARN [UserService] 主人已登录, IP:
11:26:22 WARN [UserService] 主人已登录, IP:
11:29:29 WARN [AllExceptionsFilter] IP: 错误信息: (404) Cannot GET /api/v2/init?t=Path: /api/v2/init?t=
11:29:30 WARN [UserService] 主人已登录, IP:
11:29:31 WARN [UserService] 主人已登录, IP:
11:29:38 WARN [UserService] 主人已登录, IP:
11:30:04 WARN [AllExceptionsFilter] IP: 错误信息: (404) Cannot GET /owa/auth/logon.aspx?url=https%3a%2f%2f1%2fecp%2f Path: /owa/auth/logon.aspx?url=
Followed the exact set up steps for docker, after launching the core, the following error message appears in the log file.
[Nest] 1 - 03/19/2024, 8:37:25 AM LOG 数据目录已经建好：/root/.mx-space
[Nest] 1 - 03/19/2024, 8:37:25 AM LOG 临时目录已经建好：/tmp/mx-space
[Nest] 1 - 03/19/2024, 8:37:25 AM LOG 日志目录已经建好：/root/.mx-space/log
[Nest] 1 - 03/19/2024, 8:37:25 AM LOG 资源目录已经建好：/root/.mx-space/assets
[Nest] 1 - 03/19/2024, 8:37:25 AM LOG 文件存放目录已经建好：/root/.mx-space/static
[Nest] 1 - 03/19/2024, 8:37:25 AM LOG 文件回收站目录已经建好：/tmp/mx-space/trash
cwd: /app
[Nest] 1 - 03/19/2024, 8:37:26 AM ERROR [ExceptionHandler] Invalid count value: -2
RangeError: Invalid count value: -2
at String.repeat (<anonymous>)
at JWTService.init (/app/entrypoints.js:2:524440)
at new JWTService (/app/entrypoints.js:2:524121)
at Injector.instantiateClass (/app/entrypoints.js:45:207438)
at callback (/app/entrypoints.js:45:200650)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Injector.resolveConstructorParams (/app/entrypoints.js:45:202412)
at async Injector.loadInstance (/app/entrypoints.js:45:200760)
at async Injector.loadProvider (/app/entrypoints.js:45:201392)
at async /app/entrypoints.js:45:212836
N/A
System:
OS: Linux 6.1 Debian GNU/Linux 12 (bookworm) 12 (bookworm)
CPU: (2) x64 AMD EPYC-Rome Processor
Memory: 1.60 GB / 3.82 GB
Container: Yes
Shell: 5.2.15 - /bin/bash
Binaries:
Node: 18.19.0 - /usr/bin/node
npm: 9.2.0 - /usr/bin/npm请问如何修改评论的排序方式
手机端的排序方式是，最新评论在前
可是电脑端的排序方式是，最老的评论在前。
我想让电脑端，最新的在前，请问可以怎么改嘛...
如题，Bark 通知现在似乎是不可用状态。
设置了正确的 Device ID，尝试填写服务器 URL 为 https://api.day.app/ 或者 https://day.app/ ，测试评论，通知均不可用。
值得一提的是，这个 https://day.app/ 默认值似乎并不生效：
As desc.
No need.pnpm
This 0day exists in version 3.7.7 to 3.11.4, please Upgrade to 3.11.5 or later.
后台界面上出现黑条，因为我是mx-space的老用户，之前老版本（一年前？）部署的时候不存在这个问题，因为之前的云服务器到期了又换了一个重新部署最新的版本，遇到了这个问题。不知道是不是自己操作出了问题。
使用docker一键部署脚本
全新的服务器，先按照前置要求配置安装docker和nvm之后，使用一键部署脚本，初始化后台就会遇到这个问题，但是可以继续初始化个人信息
System:
OS: Linux 4.19 Debian GNU/Linux 10 (buster) 10 (buster)
CPU: (2) x64 AMD EPYC 7K62 48-Core Processor
Memory: 166.41 MB / 1.70 GB
Container: Yes
Shell: 5.0.3 - /bin/bash
Binaries:
Node: 18.14.2 - ~/.nvm/versions/node/v18.14.2/bin/node
npm: 9.5.0 - ~/.nvm/versions/node/v18.14.2/bin/npmpnpm
在尝试最新release中的包运行 index.js 时报错，初步分析是因为某个debug文件缺失。
日志：
https://pb.envs.net/?3c853ac794a27ed8#85i9LSkNvLmpbQo5cXJeMXsFp5r7meswHZdT5iAiXE2f
从release中下载release-linux.zip，解压后运行 node index.js
System:
OS: Linux 6.4 Arch Linux
CPU: (12) x64 AMD Ryzen 5 5600U with Radeon Graphics
Memory: 1.94 GB / 13.51 GB
Container: Yes
Shell: 3.6.1 - /usr/bin/fish
Binaries:
Node: 16.20.1 - ~/.local/share/nvm/v16.20.1/bin/node
Yarn: 1.22.19 - /usr/bin/yarn
npm: 8.19.4 - ~/.local/share/nvm/v16.20.1/bin/npmn/a
如题
cravatar 有时候不是很好用（
在设置里面加一个选项，让用户自定义 Gravatar 镜像源
No response
No response
如题
在 mx-admin 后台删除已经同步到 xlog 的文章，在 xlog 的这篇文章不会随着 mx space 的删除而删除
新建文章，发布，同步到 xlog，删除文章，查看 xlog
System：
root@Nya:/opt/mx-space/core# npx envinfo --system --binaries --browsers
Need to install the following packages:
[email protected]
Ok to proceed? (y) y
System:
OS: Linux 6.7 Debian GNU/Linux 12 (bookworm) 12 (bookworm)
CPU: (4) x64 Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz
Memory: 2.28 GB / 3.83 GB
Container: Yes
Shell: 5.2.15 - /bin/bash
Binaries:
Node: 18.19.0 - /usr/bin/node
npm: 9.2.0 - /usr/bin/npm
pnpm: 8.15.4 - /usr/local/bin/pnpm
root@Nya:/opt/mx-space/core#API：
{"name":"@mx-space/core","author":"Innei <https://innei.ren>","version":"5.4.4","homepage":"https://github.com/mx-space/core#readme","issues":"https://github.com/mx-space/core/issues"}
操作信息：
操作系统 Ubuntu / 20.04 LTS amd64 (64bit)
面板版本: 3.27.1
系统版本：3.42.4
Linux version 5.4.0-109-generic (buildd@ubuntu) (gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1)) mx-space/kami#123-Ubuntu SMP Fri Apr 8 09:10:54 UTC 2022
问题经过：
有推送【管理中台】新版本，然后去kami文件夹里面执行了一下pnpm i 。
日志信息显示：
root@yuano:~/mx-space/kami# pnpm i
Scope: all 2 workspace projects
WARN deprecated [email protected]: Please use @jridgewell/sourcemap-codec instead
packages/kami-design | WARN deprecated [email protected]
WARN GET https://registry.npmjs.org/@esbuild%2Flinux-riscv64 error (ECONNRESET). Will retry in 10 seconds. 2 retries left.
WARN GET https://registry.npmjs.org/@esbuild%2Fandroid-x64 error (ECONNRESET). Will retry in 10 seconds. 2 retries left.
WARN GET https://registry.npmjs.org/@esbuild%2Fdarwin-arm64 error (ECONNRESET). Will retry in 10 seconds. 2 retries left.
Packages: +50 -93
++++++++++++++++++++++++++++++++++------------------------------------------------------------------
Progress: resolved 760, reused 705, downloaded 22, added 50, done
node_modules/.pnpm/[email protected]/node_modules/esbuild: Running postinstall script, done in 91ms
dependencies:
- react-intersection-observer 9.4.2
+ react-intersection-observer 9.4.3
- swr 2.0.3
+ swr 2.1.0
devDependencies:
- @innei/eslint-config-react-ts 0.9.7
+ @innei/eslint-config-react-ts 0.9.8
- @innei/prettier 0.9.7
+ @innei/prettier 0.9.8
- @next/bundle-analyzer 13.1.6
+ @next/bundle-analyzer 13.2.4
- @trivago/prettier-plugin-sort-imports 4.1.0
+ @trivago/prettier-plugin-sort-imports 4.1.1
- @types/node 18.14.1
+ @types/node 18.14.6
- @types/validator 13.7.12
+ @types/validator 13.7.13
- eslint 8.34.0
+ eslint 8.35.0
- zx 7.1.1
+ zx 7.2.0
WARN Issues with peer dependencies found
.
├─┬ next 13.1.6
│ └─┬ styled-jsx 5.1.1
│ └── ✕ missing peer @babel/core@"*"
└─┬ react-countup 6.4.1
└─┬ @rollup/plugin-babel 6.0.3
└── ✕ missing peer @babel/core@^7.0.0
Peer dependencies that should be installed:
@babel/core@">=7.0.0 <8.0.0"
packages/kami-design
├─┬ @floating-ui/react-dom 1.1.0
│ └── ✕ missing peer react-dom@>=16.8.0
├─┬ react-transition-group 4.4.5
│ └── ✕ missing peer react-dom@>=16.6.0
└─┬ rollup-plugin-windicss 1.8.10
└── ✕ unmet peer rollup@^2.0.0: found 3.18.0
Peer dependencies that should be installed:
react-dom@>=16.8.0
The integrity of 1670 files was checked. This might have caused installation to take longer.
Done in 1m 47.1s
问了一下chatGPT 它让我
这个错误提示显示安装过程中出现了Git访问权限问题，具体是尝试使用SSH协议从GitHub获取一个依赖库时发生的错误。你可以尝试以下解决方法：
确认你已经配置好了Git和SSH key。如果你还没有生成SSH key，可以参考GitHub官方文档进行配置。
确认你有权限访问这个依赖库。你可以在命令行中使用 ssh -T [email protected] 来测试你的Git访问权限是否正常。
如果你已经配置好了SSH key，并且有访问权限，但是问题仍然存在，那么你可以尝试使用HTTPS协议进行Git操作，例如 https://github.com/Innei/react-smooth-number-counter.git。
如果你的依赖库确实是私有库，你需要确认你的SSH key是否已经添加到你的GitHub账户，并且你的依赖库是否已经添加你的SSH key到其访问列表中。
最后，如果你仍然无法解决问题，你可以尝试在浏览器中打开依赖库的地址，以确认是否存在任何问题。如果是这样，请联系库的维护者以解决问题。
根据做了之后，然后还是无法使用pnpm i 进行更新，然后后台也崩了。
请问如何解决呀...裂开了..
与 #1232 症状类似，但只有已读页报错。
版本为最新：
在管理面板中点击评论选项卡->点击已读
System:
OS: Linux 5.4 Alpine Linux
CPU: (2) x64 Intel(R) Xeon(R) Platinum 8269CY CPU @ 2.50GHz
Memory: 128.89 MB / 919.82 MB
Container: Yes
Shell: 1.36.1 - /bin/ash
Binaries:
Node: 20.10.0 - /usr/local/bin/node
Yarn: 1.22.19 - /usr/local/bin/yarn
npm: 10.2.3 - /usr/local/bin/npmnpm
如题 管理面板无法管理评论
后端日志如下
mx-server | 10:49:02 ERROR [Catch] Schema hasn't been registered for model "Post".
mx-server | Use mongoose.model(name, schema)
mx-server |
mx-server | Use mongoose.model(name, schema)
mx-server | at NativeConnection.Connection.model (index.js:200:4337)
mx-server | at _getModelFromConn (index.js:555:1606)
mx-server | at addModelNamesToMap (index.js:555:344)
mx-server | at getModelsMapForPopulate (index.js:549:12088)
mx-server | at populate (index.js:669:601)
mx-server | at _populate (index.js:666:8356)
mx-server | at index.js:666:8179
mx-server | at new Promise (<anonymous>)
mx-server | at Function.populate (index.js:666:8156)
mx-server | at oe.Query._find (index.js:742:1047)
mx-server | at runMicrotasks (<anonymous>)
mx-server | at processTicksAndRejections (node:internal/process/task_queues:96:5)
mx-server | at async oe.Query.exec (index.js:758:5133)
mx-server | at async Promise.all (index 1)
mx-server | at async CommentService.getComments (index.js:2:157811)
mx-server | at async CommentController.getRecentlyComments (index.js:2:135455)
在管理面板中点击评论选项卡
System:
OS: Linux 5.10 Debian GNU/Linux 11 (bullseye) 11 (bullseye)
CPU: (1) x64 DO-Premium-Intel
Memory: 977.62 MB / 1.92 GB
Container: Yes
Shell: 5.8 - /usr/bin/zsh
Binaries:
Node: 20.5.1 - /usr/bin/node
Yarn: 1.22.19 - /usr/bin/yarn
npm: 9.8.0 - /usr/bin/npm
pnpm: 8.7.4 - ~/.local/share/pnpm/pnpmpnpm
如题，我按照这篇文章的方法通过 Docker 搭建了后端，随后我无论是在本地还是在 Vercel 上搭建前端（Kami 和 Shiro 都试过），前端无法验证我是主人的身份
我通过 DevTools 查看 Cookies，发现前端和后端都是存在 mx-token 这个 Cookie 的，并且值一模一样
我分别在 3 台服务器上重试过，但无论是使用 Docker 还是手动部署，都存在该问题
我认为这是一个 Bug，如果不是，我想求助是我在部署的过程中疏漏了哪一步吗
谢谢！
没看懂这一项
Server 1：
root@NekoServer:~# npx envinfo --system --binaries --browsers
System:
OS: Linux 6.5 Ubuntu 20.04.6 LTS (Focal Fossa)
CPU: (2) x64 DO-Premium-Intel
Memory: 886.35 MB / 1.92 GB
Container: Yes
Shell: 5.0.17 - /bin/bash
Binaries:
Node: 18.17.1 - ~/.nvm/versions/node/v18.17.1/bin/node
npm: 9.6.7 - ~/.nvm/versions/node/v18.17.1/bin/npm
pnpm: 8.7.4 - /usr/bin/pnpm
root@NekoServer:~#Server 2：
root@RainYun-cAI2P5IC:/opt/mx-space/Shiro# npx envinfo --system --binaries --browsers
Need to install the following packages:
[email protected]
Ok to proceed? (y) y
System:
OS: Linux 5.4 Ubuntu 20.04.6 LTS (Focal Fossa)
CPU: (8) x64 Intel(R) Xeon(R) CPU E5-2680 v4 @ 2.40GHz
Memory: 13.42 GB / 15.63 GB
Container: Yes
Shell: 5.0.17 - /bin/bash
Binaries:
Node: 20.5.1 - /usr/bin/node
Yarn: 1.22.19 - /usr/bin/yarn
npm: 10.2.0 - /usr/bin/npm
pnpm: 8.9.0 - /usr/bin/pnpm
root@RainYun-cAI2P5IC:/opt/mx-space/Shiro#Server 3：
root@138:~# npx envinfo --system --binaries --browsers
Need to install the following packages:
[email protected]
Ok to proceed? (y) y
System:
OS: Linux 6.1 Debian GNU/Linux 11 (bullseye) 11 (bullseye)
CPU: (2) arm64 Neoverse-N1
Memory: 6.62 GB / 8.00 GB
Container: Yes
Shell: 5.1.4 - /bin/bash
Binaries:
Node: 18.17.1 - /usr/bin/node
npm: 10.1.0 - /usr/bin/npm
npm notice
npm notice New minor version of npm available! 10.1.0 -> 10.2.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.2.0
npm notice Run npm install -g [email protected] to update!
npm notice
root@138:~#三台服务器 Docker 均使用 get.docker.com 的脚本安装，均使用的是该仓库中的 docker-compose.yml
n/a
配置后，点击保存。刷新页面后，SecretKey为空，估计后台没有保存上。、
shiro报错信息：
⨯ InvalidArgument: Invalid Argument: Credential access key has length 0, should be 32 at throwDefaultError (/app/node_modules/.pnpm/@[email protected]/node_modules/@smithy/smithy-client/dist-cjs/index.js:838:20) at /app/node_modules/.pnpm/@[email protected]/node_modules/@smithy/smithy-client/dist-cjs/index.js:847:5 at de_CommandError (/app/node_modules/.pnpm/@[email protected]/node_modules/@aws-sdk/client-s3/dist-cjs/index.js:4756:14) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async /app/node_modules/.pnpm/@[email protected]/node_modules/@smithy/middleware-serde/dist-cjs/index.js:35:20 at async /app/node_modules/.pnpm/@[email protected]/node_modules/@aws-sdk/middleware-signing/dist-cjs/index.js:225:18 at async /app/node_modules/.pnpm/@[email protected]/node_modules/@smithy/middleware-retry/dist-cjs/index.js:320:38 at async /app/node_modules/.pnpm/@[email protected]/node_modules/@aws-sdk/middleware-flexible-checksums/dist-cjs/index.js:173:18 at async /app/node_modules/.pnpm/@[email protected]/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:97:20 at async /app/node_modules/.pnpm/@[email protected]/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:120:14 {
admin后台点击文件上传，页面没有响应。文件也无法上传
面板版本: 4.2.7
系统版本：5.5.6如题，在尝试部署到 Zeabur 时，出现以下报错：
尝试关闭Redis的强制要求密码后，结果如下：
在本地（Arch Linux with Node.js 16.20.1）运行（连接到其数据库），出现了以下错误：
这是我所使用的脚本，并且已经确保所引用的环境变量均存在且有效：
https://github.com/BlockG-ws/mxspace-z/blob/master/run.sh
使用 zeabur 部署时所使用的 Docker 镜像为 node:16-alpine。
和 zeabur 相关人员讨论后，发现可能涉及的issue：
redis/ioredis#553
看了一下swagger，基本没有返回类型。想用swagger-typescript-api自动生成接口请求方法，结果只有请求参数能用，返回的类型基本上是any或void
在创建文章时使用自定义创建时间
浏览器请求的载荷为
{"categoryId":"65a7b67cd84b6796bb76a6ce","slug":"test","text":"test","title":"test","copyright":true,"tags":[],"summary":null,"allowComment":true,"images":[],"pin":false,"pinOrder":1,"relatedId":[],"created":"2024-01-01T10:28:00.000Z"}
服务端响应为
{
"id": "65b8cf36c4315ff3686098fd",
"created": "2024-01-30T10:28:06.948Z",
"comments_index": 0,
"allow_comment": true,
"title": "test",
"text": "test",
"images": [],
"modified": null,
"slug": "test",
"summary": null,
"category_id": "65a7b67cd84b6796bb76a6ce",
"copyright": true,
"tags": [],
"count": {
"read": 0,
"like": 0
},
"pin": null,
"pin_order": null,
"related": [],
"meta": null,
"category": {
"id": "65a7b67cd84b6796bb76a6ce",
"name": "默认分类",
"type": 0,
"slug": "default",
"created": "2024-01-17T11:14:04.179Z"
}
}两个 created 参数不一致 可见自定义创建时间并没有生效
在创建文章时使用自定义创建时间
System:
OS: Linux 5.10 Debian GNU/Linux 11 (bullseye) 11 (bullseye)
CPU: (1) x64 Intel(R) Xeon(R) CPU E5-2673 v4 @ 2.30GHz
Memory: 155.74 MB / 914.01 MB
Container: Yes
Shell: 5.8 - /usr/bin/zsh
Binaries:
Node: 20.5.1 - /usr/bin/node
npm: 9.8.0 - /usr/bin/npm
pnpm: 8.6.12 - /usr/bin/pnpm
Endpoint:
https://mx-backend.rikko.moe/api/v2目前已经重新部署了两次，仍然是无法进入后台
按照官网 https://mx-space.js.org/docs/docker 部署并完成 /qaqdmin#/setup 初始化就会出现
System:
OS: Linux 3.10 CentOS Linux 7 (Core)
CPU: (2) x64 AMD EPYC 7K62 48-Core Processor
Memory: 87.70 MB / 1.95 GB
Container: Yes
Shell: 4.2.46 - /bin/bash
Binaries:
Node: 16.9.0 - /usr/bin/node
Yarn: 1.22.22 - /usr/bin/yarn
npm: 7.21.1 - /usr/bin/npm1h1g的可以部署吗？
当友链被移动到 过时，拒绝 后，如果使用原来的信息重新申请友链，将会被提示重复。
申请友链，移动到拒绝，重新申请，即可复现
System:
OS: Linux 6.1 Manjaro Linux
CPU: (16) x64 AMD Ryzen 7 5800H with Radeon Graphics
Memory: 7.66 GB / 14.98 GB
Container: Yes
Shell: 5.9 - /usr/bin/zsh
Binaries:
Node: 16.18.1 - ~/.nvm/versions/node/v16.18.1/bin/node
Yarn: 1.22.19 - ~/.nvm/versions/node/v16.18.1/bin/yarn
npm: 8.19.2 - ~/.nvm/versions/node/v16.18.1/bin/npm
Browsers:
Firefox: 108.0.1pnpm
如题，
升级了 v5.0.0 后端，访客在评论之后，发给博主的通知邮件中 IP 和 Agent 是空的
走cf和腾讯云edgeone都试了，结果都是一样
看后台 IP 是获取正常的
是我应该在模板编辑中修改什么吗 🤔
打开邮件评论，以访客的身份发一个评论
System：
Need to install the following packages:
[email protected]
Ok to proceed? (y) y
System:
OS: Linux 6.1 Debian GNU/Linux 12 (bookworm) 12 (bookworm)
CPU: (2) x64 Intel(R) Xeon(R) Platinum 8255C CPU @ 2.50GHz
Memory: 824.09 MB / 1.80 GB
Container: Yes
Shell: 5.2.15 - /bin/bash
Binaries:
Node: 18.19.0 - /usr/bin/node
npm: 9.2.0 - /usr/bin/npm
pnpm: 8.15.2 - /usr/local/bin/pnpmAPI：
{"name":"@mx-space/core","author":"Innei <https://innei.ren>","version":"5.0.0","homepage":"https://github.com/mx-space/core#readme","issues":"https://github.com/mx-space/core/issues"}
当前后端查看 IPv6 问题（获取中）貌似是 api 接口不支持 IPv6 地址查询
/api/v2/tools/ip/240e:xxx:xxx:xxxx:xxxx:xxxx:xxxx:xxxx?t=1675938758400
请求方法: GET
状态代码: 504
更换支持 IPv6 的查询接口
No response
No response
后台无法上传文件，选择文件后没有上传按钮，页面也没有响应
后台无法上传文件，选择文件后没有上传按钮，页面也没有响应
面板版本: 4.2.5
系统版本：5.5.5no need
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.