← 变更日志

v0.6.5

A hardening and reach release. Reported security issues are fixed (see Security below), the container→host control channel is provisioned and diagnosed end to end instead of failing quietly, and Openship now installs on any mainstream Linux — and on hosts where you don't log in as root. It also adds openship edge (the whole reverse proxy from the terminal), real resource limits that respect the machine you own, an Openship Mail product shell with split outbound delivery, webmail rebuilt as an ordinary catalog app, and five new one-click apps.

1 发布
8月11日2026v0.6.5特点修复安全性73 更新

安全性

  • 安全修复

    This release resolves a number of reported security issues, with regression tests added for each. Areas touched: authorization on instance-wide and GitHub operations, access-token minting, path handling, the mail engine, webmail's HTML sanitizer, the desktop shell, and redaction in stored build output. Details are published as advisories on the repository. 建议升级。

  • 硬化

    Host-control operations are pinned to the host channel rather than defaulting to the API process's own container, cloud builds can never run on the API host, and stored SSH key material is encrypted at rest and stripped from any cross-host export.

主机控制通道

  • openship up 提供容器→主机通道,并在无法提供时告诉您

    When Openship runs in Docker, a handful of operations are genuinely host-level (freeing a foreign proxy off :80/:443、主机系统配置、邮件引擎、编写目录应用程序生成的配置),并且它们通过内部网桥上的 SSH 到达主机。现在安装生成密钥,附加受限制的 from=- 固定 authorized_keys 行,检查 sshd 是否侦听容器可以到达的地址,在主机运行的任何防火墙中打开端口,并验证往返 - 而不是在几周后的第一次主机操作上报告成功和失败。

  • 它会探测每一层,因为故障看起来没什么

    This address is host-local, so it traverses filter/INPUT 其中默认拒绝 ufw 生活;已发布的容器端口经过 DNAT 处理并跳过它,这正是为什么堆栈的其余部分看起来很健康,而这个通道挂起的原因。防火墙、sshd 监听地址、密钥和可达性均被单独探测和报告。

  • 一种解释,五个表面

    The CLI preflight, the API's boot banner, openship doctor、仪表板的服务器横幅以及主机操作死掉的部署日志已经转移到不同的故事中。他们现在从一个共享的词汇中读取内容,因为每一行要么是“你的安装没问题,这个功能不行”,要么是“你的安装坏了”——读错了的操作员要么拆掉一个正在工作的盒子,要么忽略一个失效的功能几个月。

  • openship update 修复未配置的通道

    An install from before this work, or a raw docker compose 安装,可以通过更新修复到位,而不是重新运行 up 并冒着环境风险。需要通道的部署在每次部署之前在扇出之前发出一次通知,而不是每个服务一次。

  • 该频道必须是root,并这么说

    An operation that needs a root-owned path fails with the actual cause instead of mkdir: cannot create directory '/root': Permission denied.

  • 记录了手动安装

    .env.example 详细说明所有五个步骤(密钥、受限授权密钥行、sshd 侦听地址、防火墙规则、重新创建 api,因为 env_file: 在容器创建时读取),以及一个新的 故障排除页面 步行修复。

任何 Linux 以及非 root 的主机

  • OpenShip 安装在它一直声称的发行版上

    Docker installation was curl get.docker.com | sh 在每个 Linux 上,都有一个硬拒绝 Amazon Linux、AlmaLinux、Oracle Linux 和 Alpine 的脚本。每个调用站点都有自己的包管理器表(有五个,但他们不同意),自己的 systemd 测试,以及自己对“我的白名单之外的主机”的解读 - 总是“无事可做”。主机事实现在来自一个检测器,作用于它们的命令位于一个模块中,添加发行版是一种编译错误,而不是静默的无操作。

  • 工作中的 Docker 引擎永远不会被隐式替换

    Only an explicit reinstall overrides an engine that's already running, and an installer that skips an already-working component says so instead of leaving the one actionable line nowhere at all.

  • 以非 root 用户身份进行部署是可行的

    Three layers answered "may I do root-owned work here?" differently: component installs gated properly, toolchain installs never gated at all, and the server state store assumed the login was root. There's now one privilege resolver, and it elevates the write rather than the verify (so a sudo shell 永远不会解析不同的 $HOME)。无法报告 uid 的强制命令主机不再被告知“以 root 身份连接”,这与其修复相反。

  • 语言工具链按主机安装,而不是按假设安装

    The toolchain catalog and installer were rewritten onto the same host profile, so a bare-metal build on a non-Debian box gets its runtime installed instead of a not found 在构建时。

`openship edge`

  • 整个反向代理,从终端

    A new top-level command: edge up 代理站起来并提供服务 :80/:443, edge migrate 接管现有的 nginx/Apache/Caddy 并导入其站点, edge takeover 和 edge free 声称拥有港口, edge sites 列出可以导入的内容,以及 edge repair 诊断它不服务的原因(--fix 解决端口冲突)。

  • 无需打开仪表板即可了解域、规则和流量

    edge domains add app.example.com --port 8080 针对端口注册主机名并颁发证书; edge rules 管理每条路线的速率限制、禁令和地理/CIDR 访问;和 edge traffic, edge analytics 和 edge logs 读取代理已经记录的内容。主机操作仅限于 Linux;控制平面部分可以在任何机器(包括桌面)上运行,无论上下文处于活动状态。

  • 记录为参考和演练

    A new 边缘 任务指南和完整的 命令参考.

资源限制

  • 自托管容器默认无限制

    A self-hosted project silently inherited the cloud free tier (0.5 vCPU · 512 MB) and OOM-killed memory-hungry images. On your own box the container's real ceiling is the machine, so 0 (无限制)现在是默认设置,每个消费者在应用上限之前都会测试限制。

  • 定制上限以实际机器为准

    Caps were validated against hardcoded constants (4 cores / 8192 MB), so a 64 GB box could not be told to give a container more than 8 GB. The ceiling is read from the Docker daemon's own /info (NCPU, MemTotal) — 对于本地套接字和池化 SSH 桥上的远程守护程序来说是相同的 — 当无法访问 Docker 时回退到操作系统。云没有变化:计量工作区的大小仍然根据层表确定。

  • 预检部署目标容量

    A cap larger than the host can allocate is rejected before any build work starts, with the machine's real numbers in the message.

OpenShip 邮件

  • 将实例作为邮件产品运行

    An instance can present itself as Openship Mail (OPENSHIP_PRODUCT,或设置中的切换):左栏成为邮件控制平面 - 十个管理选项卡提升为跨三个标题的导航条目,加上操作员仍然需要的主机和设置行 - 并且平台导航被隐藏。这只是演示,绝不是授权边界:Webmail 仍然通过普通项目管道进行部署,因此平台端点保持活动状态。云始终是完整的平台。

  • 在邮件服务器之间切换

    The mail surfaces are scoped to a selected server rather than assuming one, with a switcher in the shell and the scope carried through the admin tabs.

  • 出站中继提供商是真实身份

    The relay code carried a "ses" | "custom" 联合,因此 SendGrid、Mailgun 和 Postmark 在保存时就失去了身份:不包括 SPF,UI 中没有往返,添加提供程序意味着编辑 if 在服务中,DNS 构建器和扫描器。每个提供商的事实现在是所有三个都读取的数据,并且拆分交付(在这里接收,通过其他人发送)是一流的设置。

  • “邮件真的是从这个盒子里发出来的吗?”

    The daemon sweep reports that nine processes are running, which says nothing about whether Postfix can hand a message to the next hop. One wrong character in a relay password gave nine green daemons, green DNS, a Test-tab email that reported success (our Postfix accepts and queues before the relay hop), and mail that quietly deferred forever. Outbound delivery is now probed and surfaced on its own, with a reworked Health tab and a summary that names the failing hop.

  • 邮件控制台

    Live engine output in the dashboard, so a setup that stalls can be read rather than guessed at.

  • 您可以安排的备份

    The mail admin Backup tab gains a real schedule and retention plan, wired to the same pruning the rest of Openship uses.

  • 设置更早、更清晰地失败

    A preflight checks the things that used to surface mid-stream (password shape, firewall step, DNS), and setup errors render in a banner instead of vanishing into the stream.

网络邮件

  • Webmail 现在是一个普通的目录应用程序

    It installs through the same generic installer, image, volume and routing pipeline as every other app, and installs from /apps just as well as from /emails. The mail-specific part is the only part that stayed: which IMAP/SMTP backend it belongs to — one of your Openship mail servers, or an external provider.

  • 链接被存储,而不是从 slug 中解析出来

    The old lookup read webmail-<serverId> 从项目 slug 中退出,通用安装程序永远不会生成该项目,并且错误链接了某人碰巧命名为“Webmail Prod”的任何项目。现在,它是一个真正的外键,当删除 Webmail 项目时,它会被清空(不是孤立),并带有一个遗留的 slug 回退功能,该回退功能会在第一次解析预先存在的安装时对该列进行标记。

  • 它自己的图像和数据库引导程序

    A dedicated webmail Dockerfile and a bootstrap script, so first boot provisions its schema instead of depending on the mail engine's.

应用目录

  • 五个新的一键式应用程序

    Meilisearch, Redis, PostHog, Umami and Neon (Postgres), each declaring its internal connection so it can be linked into a project over the internal network.

  • 徽章告诉您正在安装什么

    Verified, unverified and hosting-mode badges with explanatory tooltips, so a community template isn't visually indistinguishable from one Openship has booted and checked.

  • 目录架构更新

    The published app.schema.json 获取上述后面的字段,并围绕它们重写了参考文档和“添加应用程序”指南。

路由和域

  • 部署会停止擦除您的 vercel.json 路由

    registerRoute 替换整个虚拟主机,因此省略了调用者 cleanUrls / redirects / headers 它没有留下它们,而是删除了它们。这些字段是在两个地方内联构建的,因此简单的部署既不会应用它们也不会保留它们,并且不相关的重新部署会默默地删除“重试路由”安装的任何内容。现在,它们在每个路线注册站点都带有的纯模块中编译一次。

  • 关于边缘拨号的一项决定

    A single resolver owns the proxy_pass 目标:默认情况下固定的环回主机端口(重新启动后稳定,从不面向互联网),容器的桥接 IP 作为高级选项,以及透明回退到不发布主机端口的内部 Compose 服务的容器 IP。每个实例均可选择,其中 auto 作为默认值。

  • 域重定向在证书颁发后仍然存在

    The redirect installed for a hostname is no longer reverted the moment certbot succeeds, and it no longer re-fires on internal rewrites.

  • 边缘的真实客户端 IP

    The real-IP configuration is derived in one place for every scope, so free subdomains and custom domains agree on what the visitor's address is.

  • 路由规则具有端到端套件

    Per-route rate limits, bans and access rules are covered by an e2e test that drives the real proxy.

DNS

  • Cloudflare DNS,有线连接

    Connect a Cloudflare token and Openship writes the records a domain needs itself (#37), issues wildcard certificates over the DNS-01 challenge, and can route a domain through a tunnel instead of an open port.

  • 我们只触及我们创建的记录

    The provider claims a record it wrote and leaves everything else in the zone alone, and it refuses to write a hostname it hasn't claimed. Deleting a domain in Openship therefore cannot remove a record that was already there.

服务器

  • 一种添加服务器表单

    The page and the modal were two 400-line forks that had drifted; they're now one component with a variant, so a field added in one place exists in both.

  • 粘贴或上传 SSH 私钥

    ssh_key_path 指向 API 主机上的文件,该文件在您的密钥位于您自己的笔记本电脑上的远程或 VPS 实例上毫无用处。现在可以从任何浏览器粘贴或上传密钥,静态加密存储,永远不会序列化回客户端,并且在存在时优先于磁盘路径。

  • 服务器页面的连接横幅本身就说明了一切

    Reachability, host channel state, and what each one does or doesn't affect, rather than a single red dot.

  • 部署默认值无法设置为派生值

    The instance default target is a server or cloud; "this machine" is derived (on a server-host box it is already in the server list), so it's no longer an option that means two different things.

项目和部署

  • 从项目标题重命名项目

    A rename modal, plus copy-id and pause/resume, on the heading where the name actually is. The slug stays immutable (it's infrastructure identity); the display name is free.

  • 容器操作通过一根管道

    Pause, restart and logs run through the same deployment-runtime path as everything else, so they can't disagree with the platform about which host or runtime a service lives on.

  • 协调和拆卸更加稳定

    Record-only deletes, orphan GC scheduling, pending actions and port checks were tightened around the same runtime path.

  • 项目的源代码、构建和运行时是三个独立的东西

    Two boolean flags (hasBuild, hasServer)每个都代表两个不同的问题,因此部署可以被接受,然后在一个阶段后失败。现在,项目由三个正交轴描述 - 代码来自何处(git、预构建图像或上传)、构建方式(Docker文件、构建包、静态或无需构建)以及随后运行的内容(Web、worker 或静态) - 在每个阶段读取的一个位置进行解析。现有项目的分类与以前完全相同。

  • 私人存储库 Docker 文件应用再次克隆

    A Dockerfile build runs no buildpack step, so it naturally carried hasBuild=false,而决定是否获取克隆令牌的一个门则关闭了该标志 - 删除令牌并使私有存储库上的克隆失败,即使 Docker 文件需要存储库作为其构建上下文。现在是否获取代码仅取决于它来自哪里,而不取决于它是如何构建的。

  • Worker 是一流的部署类型

    A long-running process with no port (a queue consumer, a bot, a cron loop) had nowhere to go: called a server it failed preflight for a missing port, called static it was routed through file-serving and failed for a missing docroot. worker 现在是它自己的工作负载——像任何其他应用程序一样构建,作为一个始终重新启动的容器运行,没有端口和路由,并检查启动命令而不是端口。从项目的 Server / Worker / Static 开关中选择它,或设置 workload: worker 在 openship.json.

编写并安装

  • up 保留你的 .env

    A variable you set by hand is kept and marked as yours, instead of being regenerated out of a fixed key list.

  • 秘密永远不会从正在运行的安装中轮换出来

    up 检测到它会铸造现有安装已经拥有的秘密(这将使加密的环境无法解密),并拒绝而不是默默地替换它。被替换的 .env 被保留以供恢复。

  • 可以固定图像版本

    An explicit --image-version 对于版本在其映像到达注册表之前到达 npm 的情况,胜过环境和 CLI 自己的版本。

  • 外部 Postgres 数据目录被拒绝,未采用

    The volume's contents are probed before a cluster is started on top of them.

  • openship doctor 和 repair 覆盖更多

    The host channel, an unprovisioned install, and port conflicts, in the same run.

  • 采用 Compose 堆栈不再重新发布其主机端口

    A migrated 5432:5432 将绑定主机 5432 在下一次部署时与已持有的任何物体发生碰撞(通常是 OpenShip 自己的 Postgres),从而中止部署。采用仅保留集装箱港口;该服务通过项目网络上的名称进行访问,并从“域”选项卡中重新公开。该警告区分了一个在机外发布的端口 — Docker 的发布规则路由经过主机防火墙,因此可以真正从 Internet 访问它 — 从仅环回的端口,这样您就知道是否实际上放弃了任何外部访问。

  • stop_signal 和 stop_grace_period 因重新部署而感到荣幸

    A service that asks for a longer shutdown window now gets a graceful stop, with its own signal and grace period, before it's replaced or torn down, instead of being SIGKILL在写入过程中通过立即强制删除进行编辑。不选择加入的容器仍然会快速停止,因此不会增加重新部署延迟。

代理和访问控制

  • 为自动化授予一个资源(而不是整个组织)的 shell

    The only way to let something run a command was a custom-command job, whose grant reaches every server in the org and can't be narrowed. Command execution now hangs off each resource's own permission: a grant on one server (server:admin)是仅限于该框的主机 shell,以及项目的赠款(project:service:write)在该项目的服务容器内运行命令 - 没有更广泛的内容。每次运行都会使用其命令、工作目录和结果进行审核,并且在无法隔离它的运行时上拒绝容器执行。

  • AI 代理通过 MCP 执行

    Two new MCP tools expose host and in-container execution, each requiring the matching per-resource grant, with a hard timeout and an output cap (the agent's call blocks on the reply and the whole body lands in its context). Tools that only work on a self-hosted box are now hidden on the hosted platform, instead of being advertised there and returning 404.

  • 一个访问编辑器和一个实时代理可以重新确定范围

    The MCP consent screen, personal-access-token scoping and member grants were three separate editors and are now one. A connected agent's access can be edited in place from Settings — narrowed, or widened (widening to unscoped asks first) — and applies on its next request, with no disconnect-and-reconsent.

  • 您始终可以强制执行的范围现在可以授予

    Several platform areas (jobs, notifications, analytics, settings, updates, cloud) could be checked for but never handed out, so there was no middle ground between "deploy only" and "the whole account"; they're grantable now, with billing and audit marked sensitive. Listing a collection honors a wildcard grant too — a token allowed to read a server by id no longer 404s when it tries to enumerate them.

桌面

  • 本地部署受到明确的“即将推出”的限制

    Desktop mode is built to control remote servers; running the workload on the desktop itself isn't enabled yet, and the UI now says that once, in one place, instead of offering a target that fails later.

  • 外壳强化和更安全的更新程序

    See Security above.

文档和网站

  • 新的和重写的页面

    "The edge" guide, the openship edge 命令参考、主机通道故障排除、重写的“添加应用程序”指南和应用程序目录参考,以及有关安装、更新和日志/监控的说明。

  • 文档获取社交预览

    Generated OG images per page.

  • 更好的变更日志页面

    Entries collapse to headlines and expand to detail, with controls to expand or filter, driven by this file.

修复

  • 零身份验证登录不会永远反弹远程浏览器

    An instance with no sign-in form grants its session only to a browser on the same machine, so bouncing a remote one was guaranteed to fail, leaving a spinner and then either a connection error for a host that isn't yours or an endless redirect. The page now names the cause.

  • 邮件保留修剪尊重邮件备份

    Pruning no longer considers a mail engine backup an ordinary project artifact.

  • 迁移的容器加入其路由所在的网络

    A same-server migration attached a container that was never published, leaving it unreachable behind a verified domain.

  • 取消构建会停止每个构建路径

    Cancellation reached some paths and not others, so a cancelled build could still be deployed: remote Docker builds kept running, and the static extract went on to publish the output of a build you had already stopped. A cancelled deployment is now terminal.

  • 无操作组合重新部署不会接管活动版本

    A redeploy where every service was carried forward unchanged settled without advancing, so it no longer displaces the release that is actually running.

  • 存储的健康检查在设置表单中仍然存在

    Editing project settings preserved the healthcheck test rather than dropping it, and a NONE 测试数组读取为禁用而不是命令。

  • 完成的转储不再悬挂

    Exec-stream sinks close on EOF, and the upload stall bound matches the producer's idle budget, so a completed backup can't wait forever on a stream that already ended.

  • Docker文件项目不需要命令

    Projects that rely on the image's own entrypoint deploy without one.

  • 每个新字符串都会被翻译

    The release's new copy landed across all shipped languages, with the parity test extended to the new namespaces.