onetimesecret
2,991
Stars
—
Forks
0
Watchers
—
Open Issues
待补全
许可证
Ruby
语言
—
创建时间
最近更新
项目能做什么
一次性密码与敏感信息分享工具,避免机密信息留存在聊天记录或邮箱中。
来源:基于仓库元数据
· 内容以仓库实际 README 为准
使用说明 查看原始 README 原仓库文档
中文使用说明暂未生成。下面保留原仓库 README 摘录,命令与配置均以原文为准。
原始 README 摘录(英文原文,节选前 3000 字符)
# Onetime Secret — Secure One-Time Message Sharing
_Keep passwords and other sensitive information out of your chat logs and emails._
A **one-time secret** is a link that can be viewed only once — a single-use URL.
When you share sensitive info like a password over email or chat, copies linger
in many places. Onetime links self-destruct after viewing, so only the intended
recipient ever sees the contents.
**[Try it live at OnetimeSecret.com →](https://onetimesecret.com/)**
## Quick Start (Docker)
```bash
# 1. Start Redis
docker run -p 6379:6379 -d redis:trixie
# 2. Generate and store a persistent secret key — back this up safely
openssl rand -hex 32 > .ots_secret && chmod 600 .ots_secret
# 3. Run Onetime Secret (set SSL=true for production)
docker run -p 3000:3000 -d \
--name onetimesecret \
--add-host=host.docker.internal:host-gateway \
-e REDIS_URL=redis://host.docker.internal:6379/0 \
-e SECRET="$(cat .ots_secret)" \
-e HOST=localhost:3000 \
-e SSL=false \
onetimesecret/onetimesecret:v0.26.14
```
Open <http://localhost:3000>, then create an admin ("colonel") account — it
prints a generated password and is verified immediately:
```bash
docker exec onetimesecret bin/ots customers create me@example.com --role colonel
```
> [!IMPORTANT]
> **Losing your `SECRET` key is not recoverable**. It makes existing
> secrets unreadable among other things, so back it up.
## Going further
- **Self-hosting** — reverse proxy, full authentication (PostgreSQL + RabbitMQ, MFA, WebAuthn), and production hardening: [Self-Hosting Guide](https://docs.onetimesecret.com/en/self-hosting/)
- **Docker Compose** — simple and full stacks: [docker/README.md](./docker/README.md)
- **Configuration** — [.env.reference](./.env.reference) and [config defaults](./etc/defaults/config.defaults.yaml)
- **Contributing** — from clone to a green test suite in two commands, plus [test accounts & API tokens](./docs/development/test-accounts.md): [CONTRIBUTING.md](./CONTRIBUTING.md)
## Community & Support
- **Get help** — [Documentation](https://docs.onetimesecret.com) · [Report an issue](https://github.com/onetimesecret/onetimesecret/issues) · [Support](./SUPPORT.md)
- **Project** — [Latest Release](https://github.com/onetimesecret/onetimesecret/releases/latest) · [Docker Hub](https://hub.docker.com/r/onetimesecret/onetimesecret) · [Build Status](https://github.com/onetimesecret/onetimesecret/actions)
- **Policies** — [Security](./SECURITY.md) · [Code of Conduct](./CODE_OF_CONDUCT.md)
- **See also** — [Similar services & alternatives](./docs/similar-services.md)
## AI Development Assistance
Onetime Secret was developed with help from AI tools for architecture design,
code generation, and documentation. As project maintainers, we remain responsible
for all design decisions and the final code, and believe in being transparent
about the tools involved.
## License
MIT — see [LICENSE.txt](./LICENSE.txt).
阅读完整原文
项目深度分析 规则生成(AI 未配置)
综合评分 64.9 分。该项目在“个人可实施性”维度得 35 分,“付费可能性”维度得 60.0 分,差异化空间 100.0 分(评分依据见评分卡)。
将 onetimesecret 改造为垂直场景 SaaS
| 产品构想 | 保留核心能力,针对某一类用户(如某行业团队)做托管版,收取月费。 |
| 目标用户 | 有该需求的中小团队 / 独立站长 |
| 难度/周期 | 较高 · 2~4 周(MVP) |
| 收费模式 | 订阅制(如 ¥29~99/月) |
| 竞争风险 | 需验证付费意愿;注意许可证合规 |
| 依据 | 数据支持的判断:许可证与关键词显示存在商用与付费场景 |
面向细分需求的二次开发产品
| 产品构想 | 基于 onetimesecret 的核心能力,聚焦一个更窄的场景(如某平台、某行业)做差异化。 |
| 目标用户 | 该细分场景用户 |
| 难度/周期 | 中 · 2~6 周 |
| 收费模式 | 买断制 / 订阅制 / 广告 |
| 竞争风险 | 细分需求规模需验证 |
| 依据 | AI 推测:基于项目主题标签的判断 |
以上为规则引擎基于仓库公开数据生成的参考结论,包含推测成分,不构成投资或创业承诺;配置 AI 后可获得更深入的分析。
报告会保存到 个人中心
竞品与相似项目 GitHub Search 真实检索
相似项目数据正在完善中,暂不展示(避免误导)
项目优势与风险
| 技术成熟度 | 创建时间待补全,最近推送 ,发布过 100 个 Release |
| 社区活跃 | Star 2,991 / Fork 0 / Issue 0(数据支持,可自行核实) |
| 许可证 | 未检测到(需人工确认) |
| 主要风险 | 上游项目方向可能变化;同赛道竞争者较多(见竞品表);热度与需求不完全等价 |
安装与使用
此项目未提供 Docker 镜像,安装步骤以原仓库 README 为准(涉及依赖安装与环境配置,对新手门槛较高)。