← 变更日志

v0.6.1

A large release. It adds a full service-to-service networking plane, around-the-clock container health monitoring, and real analytics with visitor geography and usage history — plus a self-contained containerized mail engine, a fleet-wide infrastructure view with one-click updates, an audit log you can filter and attribute, Telegram alerts, and a Node-based installer that retires the last of the Bun crash class.

1 发布
8月7日2026v0.6.1特点修复Breaking52 更新

服务到服务网络

  • 现在任何项目都可以通过内部网络连接到另一个项目

    Every project (a plain single-app, a raw Compose stack, a monorepo, or an imported one) now shows a Connection card with its internal address (http://<alias>:<port>)并可以选择作为“在项目中使用”源。以前,只有具有声明的连接块或多服务 Compose 堆栈的目录应用程序可以在内部访问;单个应用程序项目根本没有内部地址。相同边界的可达性是自动的,并且跨越边界保持明确——只有当您将消费者链接到网络上时,别名才变得可达。仅自托管,并跳过静态站点(无侦听端口)和云托管应用程序(而是通过公共链接)。

  • 为服务提供自定义内部主机名

    A service can carry a custom east-west DNS alias that resolves alongside its default name, set from the service's Settings tab and available to single-app, Compose, and monorepo services alike. Openship normalizes it to a valid hostname and rejects one that collides with another service on the same project network, and the internal-address card shows the alias its containers actually answer to. Self-hosted only.

  • 更清晰的服务设置编辑器

    The service Settings tab groups fields into labelled sections and swaps free-text boxes for structured editors: ports and volumes are entered as chips (with per-item limits enforced as you type) and depends-on is a picker of the project's other services. The image and build-from-source fields are shown together — fill either, and a build context wins over a stale image — instead of an image/build mode toggle.

容器健康和事件

  • OpenShip 全天候监控您的容器,而不仅仅是在部署时监控

    Until now a container was health-checked exactly once, during the ~15s window right after a deploy, and then never looked at again unless a human was staring at the project page. A new health watch polls every server's Docker daemon once a minute (and reacts within about 10 seconds when Docker itself reports a container dying or restarting), so an app that falls over or drops into a crash loop at 3am raises an alert through your existing notification channels instead of waiting for a user to complain. Self-hosted only.

  • Broken containers page you once, not every minute

    A container stuck in a restart loop is broken on every poll, so a naive watcher would fire 60 alerts an hour about one fault. Instead each fault becomes a single incident: one message when it opens, one more only if it gets strictly worse (unhealthy → crash looping → down), and one all-clear that tells you how long it was down. A fault must be observed twice before it notifies, and an in-flight deploy, an operator's own docker stop,或者禁用的项目永远不会触发误报。

  • 无法访问的服务器是一个警报,而不是每个应用程序都有一个警报

    When a box's Docker daemon stops answering, Openship opens a single server-level incident that names how many projects it can no longer monitor, and freezes those projects' health rather than falsely marking them recovered. The record is durable, so a box that has been down for days does not re-page every time the control plane restarts.

  • 每个项目都有一个“运行状况”选项卡,包含 30 天的事件历史记录

    Each project gets a Health tab listing its currently open incidents plus a rolling 30-day history of resolved ones with downtime durations. It also states whether monitoring is actually switched on (an operator toggle in the Jobs module) and surfaces the server's own outage when a box is unreachable, so an empty tab is never misread as "all good." Self-hosted only.

分析和资源使用

  • 查看您的访客来自哪里

    The Monitoring tab draws a per-country choropleth of visitors alongside a ranked list, and animates real-time request ripples fed by the same stream the Logs tab tails, so you can watch where requests are landing right now. It works the same way self-hosted and on Cloud, and it can tell "no visitors yet" apart from "geo lookups aren't set up on this box," which used to render identically as an empty map. On a multi-domain project the whole view scopes to a chosen domain.

  • 访客数量现在是真实数字,而不是请求数量

    The dashboard's visitor figure was a request count relabelled "unique IPs," so five page views from one browser counted as five people. It's now a genuine count of distinct visitors, deduplicated at the edge with a per-day salted hash that never stores an address or a per-visitor row — the number is honest while still collecting no behavioural data on your end users.

  • 背后有真实数据的热门路径和响应代码

    The Top Paths table was hardcoded empty and error rate couldn't be answered from anything saved. Both are real now: the daily rollup records normalized request paths (query strings stripped, ids collapsed, so tokens never become keys) and the full status-code mix, and a new card expands each 2xx/3xx/4xx/5xx class to the exact codes beneath it. On self-hosted, per-path aggregation is opt-in per project (a toggle, default off, including on existing projects) because it adds measurable work to every request the edge handles; on Cloud paths are aggregated automatically. Every other analytics dimension is unchanged.

  • 保留使用历史记录,以便您可以查看导致崩溃的原因

    CPU, memory and network usage used to exist only as a live stream that vanished when you closed the tab, so "was memory climbing before it got OOM-killed at 3am" had no answer. Usage is now sampled on a schedule into 5-minute buckets and charted over time, per service. A Compose project reports its whole stack with a per-service breakdown and an All/service scope picker instead of just the one container the primary service owned; a static site (nothing to measure) now says so plainly instead of showing four zeroed metrics. Self-hosted Docker deployments; bare non-Docker deployments report zero network, since per-process accounting isn't available there.

  • 繁忙的域保留其分析

    A domain pushing more than about 2 GB in a single minute (roughly 286 Mbps — routine for video or large downloads) used to overflow a 32-bit byte counter and kill the analytics scrape for that entire domain, so the busiest sites were precisely the ones with no analytics. The bandwidth counters are now 64-bit and collection keeps up. Self-hosted edge.

  • 当无人查看时,分析不再悄然消失

    Traffic analytics live in the edge's memory under a TTL and were only flushed to the database when someone opened a project's Analytics tab, so a project nobody viewed for a day lost its per-minute data. A background scrape job now persists every server's analytics on a schedule whether or not anyone is watching, collecting a whole server in one pass instead of a separate memory scan per domain.

  • 每个主题中的图表工具提示都可读

    Tooltips were effectively transparent in the dark themes (plot lines showed straight through the text) and on light cards the hover marker rendered as a stray white block below the tooltip. Both are fixed with a shared tooltip style reused across the monitoring and billing charts.

边缘和反向代理

  • 调整每个项目的反向代理

    A project's Routing settings now expose a full set of proxy tunables instead of a handful: raise or entirely remove the upload size limit, set connect/read/send/keepalive timeouts, control response buffering and gzip level, turn on HTTP/2, tighten request-header limits, and verify TLS to the upstream — each value validated before it reaches the generated nginx config and labelled with its own directive name. On self-hosted it also reads back what the edge is actually serving next to what you saved, flags any drift in colour, and offers a one-click adopt, so a hand-edited vhost or a value the sanitizer dropped can't quietly disagree with your settings. Self-hosted only.

  • 每个国家/地区的分析和国家/地区规则适用于容器化边缘

    The containerized edge shipped without the MaxMind geo library or its country database, so every lookup returned nothing: no per-country analytics were recorded, and country-based route rules failed closed (a single-country ban silently blocked all traffic). The library and a GeoLite2 database — parsed and validated before shipping — are now baked into the edge image, so geo works from a box's first install with no runtime download.

  • Cloudflare 或负载均衡器背后的正确访问者身份

    Behind a proxy the edge treated the proxy as the client, which broke four things at once: visitor country resolved to the PoP, distinct-visitor counts collapsed, per-IP rate limits put the whole planet in one bucket, and IP bans banned a PoP instead of a visitor. The edge now recovers the real client address from CF-Connecting-IP,仅信任 Cloudflare 的已发布范围作为连接对等点。

  • 即使不在 API 环回上,每条路由的规则也会到达边缘

    Pushing a project's route rules to a local edge now goes through the same resolved edge-management path as the rest of Openship instead of assuming the edge lives on the API host's own loopback. On setups where it doesn't — such as the containerized edge — rate-limit, ban, and country rules now actually take effect.

  • “Edge Ready”药丸与服务器的真实状态相匹配

    Edge readiness is now read from whether Openship's edge container is actually running, the same fact the Infrastructure tab and System Health use. Before, a leftover bare-host OpenResty install could make the pill claim "ready" while the server tab reported the edge as down.

自定义和免费域名

  • 免费 .opsh.io 域仅路由到您已证明其控制权的服务器

    Openship Cloud's shared edge now forwards a free subdomain to your server only after that server answers a challenge proving it owns the target, a proof that lasts 90 days and that Cloud re-checks about a week before it lapses. Openship prepares the box to answer the moment you set up its edge, so a free domain added later works without a redeploy, and a background sweep re-asserts, reads back over the server's own public address, and re-verifies anything expired — so a box left undeployed for months no longer silently loses its free URLs. A slug can't be pointed at someone else's box, and a server that can't yet answer is told why. Requires Openship Cloud.

  • 免费和自定义域现在可以在静态网站上使用

    Adding a free .opsh.io 域名指向一个静态项目,用于在边缘注册任何内容,因此 URL 会变成通配符,后面没有来源;编辑静态项目的域在下次重新部署之前不会写入任何虚拟主机。现在,两者都会在您保存时发出真实的路线,为项目的构建文件提供服务 - 代理应用程序已经具有相同的行为。

  • 已颁发但随后遇到障碍的证书不再丢失

    If an ACME order completed but a later step failed (the vhost rewrite, the reload, or the read-back), the domain stayed stuck in "provisioning" with no expiry recorded, which made it invisible to the renewal sweep — a valid certificate then sat on the edge and expired ~90 days later. Openship now re-reads the edge after a failed issuance and records a certificate that's actually present, so renewal stays scheduled.

  • 无效的自定义域被拒之门外

    Setting a custom domain to something that isn't a public hostname (localhost、裸 IP、单个标签或带有路径/端口/方案的值)用于返回成功、创建死的挂起域行,甚至写入 server_name localhost; vhost 到共享边缘。写入路径现在验证自定义主机名并拒绝错误的主机名,同时仍然允许已经拥有错误值的项目编辑并将其删除。

  • 编辑免费域不再显示错误的“需要操作”

    A single edit could sync the same free subdomain to Cloud twice, and the two racing challenges reset each other's token, so the route worked but the project reported "Action Required" anyway. Callers that run their own managed-edge sync now suppress the duplicate, so each edit issues one challenge and the status reflects reality.

  • 重定向和上传限制在保存时生效

    Raising a route's upload limit or adjusting its timeouts now applies as soon as you save instead of waiting for the next redeploy, and a domain redirect is applied live to static-site domains too, not only to proxied apps.

电子邮件

  • 邮件作为独立引擎运行,而不是接管您的服务器

    Setting up mail no longer installs iRedMail's daemons directly onto the host or reboots the box. Postfix, Dovecot, spam and virus filtering, and DKIM now run inside a single openship-mail 容器及其 vmail 数据库位于 Postgres sidecar 中,主机联网,因此邮件仍然可以看到真实的客户端 IP,并且边缘不处于邮件数据路径之外。设置减少到八个步骤,唯一的先决条件是 Docker 和 openship 边缘,并且每个邮件状态(队列、maildirs、DKIM 密钥、配置)都位于主机绑定安装上,因此升级是一种保留数据的拉取和重新创建过程。仅自托管。

  • 邮件使用与其他所有内容相同的边缘和 TLS

    Mail setup no longer stands up its own host OpenResty and certbot on the side. The certificate for mail.<domain> 通过共享的 openship 边缘发布,与其他域的 TLS 所采用的路径相同,并且现在像任何其他域一样记录续订 — 容器化边缘上的邮件证书(无主机 certbot 计时器)用于在安装后约 90 天悄然过期;续订失败现在会发出通知。

  • 容器化之前设置的邮件服务器继续运行

    The move to containers is topology-aware, so a server whose mail was installed the old way (system daemons, database on the host) still reports accurate component health and stays fully manageable: SQL queries, outbound SES/SMTP relay config, and daemon restarts all target the right engine. When the engine genuinely is stopped or was never installed, admin actions now return a clear message telling you to restart it or re-run setup instead of a bare 500 leaking a Docker "No such container" error.

远程基础设施

  • 在一个地方查看每个托管边缘和邮件容器

    A new Infrastructure view lists each server's edge and mail container with the image version it's running against the version this release pins (for example edge 0.4.0 → 0.5.0), and flags which are behind, stopped, or missing. An attention rollup surfaces the ones that genuinely need hands — an edge that's down, or absent on a box that hosts projects — separately from the ones that merely have an update available. Self-hosted only.

  • 在不接触 shell 的情况下更新、修复或安装容器

    Update swaps a behind container onto the pinned image (rollback-guarded), Fix restarts a stopped one in place, and a server with no edge gets a one-click Install that runs the first- install path with 80/443 takeover consent. Each apply streams its pull/recreate/ verify progress and survives a dropped connection, and a fleet-wide Update all / Restart stopped does the same across every server at once. Self-hosted only.

  • 升级时自动更新您的远程基础设施

    A new instance-wide toggle lets the control plane update every remote edge and mail container automatically when you upgrade Openship (its APP_VERSION 向前移动),因此您的舰队的基础设施可以跟踪您正在运行的版本,而无需手动扫描。它是服务器端的,因此它也可以在桌面上运行,与桌面应用程序自己的自动更新不同,并且默认情况下处于关闭状态。仅自托管。

  • 漂移检测本身保持最新状态

    With auto-scan on (the default), opening the Infrastructure tab or the home page quietly runs one detect-only scan when the cached state is stale, throttled to about every 30 minutes per browser, so the attention dot reflects reality without pressing Scan. It only refreshes what's shown — it never applies an update, which stays the separate auto-update toggle. Self-hosted only.

  • 旧版盒子不再被标记为损坏

    A server converted to the containerized edge kept listing its leftover host OpenResty as a component with an Update button for a config nothing loads; those superseded host modules are now dropped from the view. And a legacy host-native mail engine (systemd Postfix/Dovecot) that was quietly delivering mail used to show up as "Stopped, container missing" — it's now labelled as not containerized rather than inventing a version. Self-hosted only.

Docker迁移

  • 迁移后的网站保留其运行时的上传限制和超时

    When you move or take over a Docker stack, the reverse-proxy tunables the source vhost declared (upload size limit, upstream read timeouts) are now carried onto the migrated project before the new edge vhost is rendered. Previously the site silently reverted to nginx's 1 MB / 60 s defaults at cutover, so the first large upload after a move failed with a 413 and nothing tied it back to the migration. Adoption is additive: a limit you set by hand always outranks a value inferred from the old box. Self-hosted only.

  • 采用堆栈不再重新发布内部端口

    A compose service that published a container port on a random host port (a single-part ports: 条目,例如数据库的 5432(源从未真正暴露)现在在采用过程中保持不暴露,而不是在目标上重新发布,因此迁移不会不必要地暴露内部服务或与已拥有主机端口的任何内容发生冲突。该端口仍然显示在向导中,以便您可以路由到该端口,并且服务到服务的流量通过共享网络继续按名称进行解析。仅自托管。

  • 向导会告诉您哪些环境变量没有被继承

    When adopting a foreign stack, environment variables that exactly match the image's baked-in defaults are dropped rather than imported as explicit config (the image still supplies them at runtime). The wizard now lists exactly which keys were skipped and why — common with Coolify/Nixpacks images that bake config as ENV layers — so you know what to re-enter if you later change the image.

  • 导入向导中不再出现虚拟主机名

    The wizard used to invent a hostname from the project name whenever a step had no route chosen, labelling port fields, previewing monorepo sub-app hosts, and even wiring the "Visit Site" button to a host that would never exist. It now shows only hosts your config actually names, and hides "Visit Site" entirely when the deployment has no public domain.

审核日志

  • 准确查看您的 AI 助手发生了什么变化

    Every audit entry now records where the action came in from (the dashboard, an MCP client, the CLI, the API, a webhook, or the system itself), and you can filter the log down to a single source. Isolating MCP-driven activity finally answers "what did the AI assistant do," which was impossible before because an MCP write and a CLI write produced identical rows. Entries written before this release show as an honest "unknown" rather than being mislabelled.

  • 关闭审核并控制其保留时间

    Each organization can switch audit recording on or off and pick a retention window (7, 30, 90, 180 or 365 days). Turning recording off stops new entries but never touches the ones already written, and the act of disabling is itself logged first, so the trail always explains why it went quiet. The switch is per-organization, so on a shared cloud instance one tenant can't disable everyone's audit log.

  • 日志上的真实过滤栏

    You can narrow by category, actor, date range and free-text search, with a live count on every category tab. Search resolves project, server and domain names, so typing a name like "api-gateway" turns up entries that only ever stored an opaque id, and rows now display the human name of the affected resource, resolved server-side in one batched lookup per page.

  • 分页日志不再跳过或重复行

    Entries that share a timestamp are now ordered by a stable tiebreaker, so scrolling through pages no longer reshuffles them; two entries created in the same instant could previously appear twice or vanish between pages.

通知

  • 向 Telegram 发送警报

    Telegram joins email, Slack, Discord, and Teams as a notification channel: point a BotFather bot at a chat, group, or forum topic and Openship delivers your deploy, health, and job alerts there. The bot token is stored encrypted, and the channel list shows which bot does the sending.

  • 自托管通知设置删除了永远无法触发的开关

    On a self-hosted box the billing notification categories are fed by the SaaS billing system, so they were switches that could never send anything. They no longer appear, and the remaining categories are organized into tabbed groups in Settings.

安装及包装

  • OpenShip 现在在 Node 上安装和更新,而不是全局 Bun

    该 curl | sh PowerShell 安装程序会下载一个在 Node 下运行的独立的、经过 sha256 验证的 CLI 有效负载:如果您有 Node 22+ 系统,它们会使用您的系统,否则会从 nodejs.org 向您提供官方 Node 22 ~/.openship,并且它们会悄悄地将您从以前的任何全局 Bun 安装中迁移出来,而无需触及您自己的 Bun。 openship update 采用相同的路径 - 重新下载经过验证的有效负载,首先刷新运行时 - 因此提升节点底层的升级会自行修复而不是破坏。这将淘汰可能会导致远程 SSH 操作的 Bun-vs-ssh2 崩溃类。

  • 邮件服务器作为官方镜像提供

    Openship's official multi-arch (amd64 + arm64) image set, built and published to GHCR and Docker Hub each release, now includes openship-mail 与 API、仪表板和边缘图像一起,因此不再需要从源代码构建自托管邮件引擎。

  • openship up 现在可以在无根 Docker 下工作,而不是神秘地失败

    Bringing up the compose stack on a rootless daemon used to abort the install with Docker's opaque "error while creating mount source path … permission denied," because a rootless daemon can't create the edge's bind-mount directories under root-owned paths. The CLI now creates those directories itself and, when it can't, prints the exact one-time sudo mkdir/chown 运行命令(#372)。

部署和编写

  • 工作部署永远不会被记录为失败

    Build output that carried a raw NUL byte or a broken Unicode character (as a failed docker exec 当它溢出其多路复用流、帧头和所有内容时,会导致日志写入失败,并且 OpenShip 误读拒绝写入,因为部署本身失败:实时运行的部署被标记为失败,其容器被拆除,而部署视图仍停留在“正在部署”。存储的构建日志现在已进行清理并限制大小,结果写入会丢弃任何日志或错误 blob Postgres 拒绝的内容,而不是丢失状态,并且始终会触发关闭实时流的终端事件。

  • 您的访问 URL 和自定义域端口在重新部署后仍然存在

    A project's deploy target is now stored durably on the project itself (a new server_id 列),而不是仅存在于最新部署的易失性元数据中。以前,新的或部分快照可能会丢失该绑定,悄悄地将项目回归到本地部署,从其自定义域中剥离端口(502),并将访问 URL 重置为 localhost:3000;现有的服务器托管项目已回填,因此在下次重新部署时不会影响它们。即使部署的端点集省略了经过验证的自定义域,也会保留它,而不是删除或清空它。仅自托管。

  • 自由域安装现在有一个部署目标

    A box set up with a free .opsh.io 域可以在没有列出任何服务器且没有任何可部署到的情况下完成加入,因为注册本地“此服务器”行会挂起路径永远不会运行的引导步骤。现在,当首次列出服务器、连接到 OpenShip Cloud 以及管理员重置时,该框会具体化其自己的部署目标行。附上免费的 .opsh.io 稍后项目的域不再需要首先重新部署,因为现在每次部署都会启动框以回答所有权检查。仅自托管。

  • 服务域尊重您的上传限制和代理设置

    A compose service's own domain ignored the project's reverse-proxy tuning, so the main app would accept a 50 MB upload while the same project's service domain rejected it at nginx's 1 MB default with a 413. Those settings now apply to every domain a project writes — per-service, static, single-domain composites, path fan-out, and single-app native deploys. Self-hosted only.

  • 目录应用程序服务 URL 按端口进行解析并且绝不为空

    Apps that route one container port to a domain and leave another port-only (Convex, for one) used to get an empty or self-referential origin injected (CONVEX_SITE_ORIGIN="",或一个 127.0.0.1 容器内的那个指向容器本身)。现在每个端口都可以独立解析,仅端口服务会回退到盒子的真实可达状态 http://host:port,和一个 {{publicUrl:…}} 仍然无法解析的令牌未设置 - 因此应用图像自己的默认值 - 部署日志中会发出响亮的警告,而不是无声的空白。

  • 路由警告会告诉您边缘何时出现问题

    When a deploy succeeds but its domains aren't being served, the post-deploy warning now checks why: if the edge container itself is down it tells you to bring the edge back up, instead of sending you off to your DNS provider to debug routes that are actually fine. Self-hosted only.

升级说明:此版本改进了固定边缘和邮件图像版本。在自托管上,打开新的基础设施视图,将每个服务器的边缘和邮件容器更新到固定映像上,或者打开实例范围的自动更新,让控制平面在每次升级时执行此操作。