Files

flying-hero 96f6318101 📦 添加虚拟环境和启动脚本

新增:
- backend/venv/ - Python 虚拟环境
- backend/start.sh - 启动脚本（使用虚拟环境）
- backend/requirements.txt - 依赖列表
- .gitignore - 忽略虚拟环境和缓存文件

说明:
- 每个项目使用独立虚拟环境
- 避免依赖冲突
- 启动脚本自动创建和激活虚拟环境

2026-04-04 18:29:02 +08:00

index.js

📦 添加虚拟环境和启动脚本

2026-04-04 18:29:02 +08:00

LICENSE.txt

📦 添加虚拟环境和启动脚本

2026-04-04 18:29:02 +08:00

package.json

📦 添加虚拟环境和启动脚本

2026-04-04 18:29:02 +08:00

README.md

📦 添加虚拟环境和启动脚本

2026-04-04 18:29:02 +08:00

signals.js

📦 添加虚拟环境和启动脚本

2026-04-04 18:29:02 +08:00

README.md

signal-exit

When you want to fire an event no matter how a process exits:

reaching the end of execution.
explicitly having process.exit(code) called.
having process.kill(pid, sig) called.
receiving a fatal signal from outside the process

Use signal-exit.

var onExit = require('signal-exit')

onExit(function (code, signal) {
  console.log('process exited!')
})

API

var remove = onExit(function (code, signal) {}, options)

The return value of the function is a function that will remove the handler.

Note that the function only fires for signals if the signal would cause the process to exit. That is, there are no other listeners, and it is a fatal signal.

Options

alwaysLast: Run this handler after any other signal or exit handlers. This causes process.emit to be monkeypatched.