* fix(mail): complete local backups and portable server restores
* test(mail): report engine diagnostics on round-trip failure
* fix(mail): stop Postfix writers before container snapshots
* fix(mail): apply Postfix shutdown in the daemon action renderer
* test(mail): install GNU tar on the remote fixture host
* fix(build): keep environment values out of Dockerfiles and logs
* test(build): exercise secret transport in deployment CI
* test(build): align cloud fixture file and command identities
* fix(build): validate secrets before allocating build resources
* fix(mail): persist mail logs, fail2ban database and ignoreip across engine updates
Mail engine updates recreate the container (docker rm -f + docker run),
so anything not on a bind mount is lost: /var/log (mail.log, dovecot and
fail2ban logs), fail2ban's SQLite database, and operator ignoreip
customisations in /etc/fail2ban.
- Bind-mount /var/log and /var/lib/fail2ban from the host mail state dir.
Deliberately not /etc/fail2ban: a seed-once mount would hide later image
changes (same trap as #392's master.cf).
- Render operator ignoreip additions (OPENSHIP_MAIL_F2B_IGNOREIP, passed
through engine.env) into a jail.d override on every boot, as baked
jail.local value + operator value, so image defaults are never dropped.
- Run cron under supervisord so logrotate's daily job actually fires for
the now-persisted logs; logrotate is installed explicitly (only a
Recommends of rsyslog) and build-gated.
Fixes#1701
* Preserve existing mail state before replacement and repair supervised log rotation
---------
Co-authored-by: Hydra <abdelhamedmo59@gmail.com>
* fix(updates): report image services with an unknown deployed digest instead of up to date
When the active service_deployment row has no image_digest — a carried
service loses it when a per-service update upserts the row — the feed
compared digests only when both were known and fell back to the equal
ref strings, so the service read as up to date and `?behind=1` dropped
the project entirely.
The deployed side is now marked unknown, not current: evaluateDrift
flags image services whose row has no digest, and the feed resolves
those against the live daemon before rendering — the running
container's image ID against the image ID the configured tag resolves
to right now, the same test the deploy pipeline uses before carrying
an unchanged service. A mismatch is behind; matching images recover
the tag's RepoDigest onto the row when the registry comparison agrees;
anything the daemon cannot answer stays unknown and the project is
kept visible with an `unverified` flag instead of being dropped.
Fixes#1702
* fix(updates): narrow the live runtime to DockerRuntime before resolving unknown digests
`resolveDeploymentRuntimeForRead` returns a `RuntimeAdapter`, and
`prepareDeploymentImage` is Docker-only, so the Typecheck job failed
with TS2345 at local-image-drift.ts:79. Guard the call with the same
`instanceof DockerRuntime` check `recordDeploymentArtifacts` uses:
other runtimes leave the services unknown, and the runtime is still
disposed on every path.
---------
Co-authored-by: Hydra <abdelhamedmo59@gmail.com>
* Render mail print metadata as text and isolate print documents
* Update application dependencies for published security advisories
* Require patched Dovecot and Pigeonhole in mail images
* feat: add platform migrations and refresh the Cloud experience
* fix(ci): run MongoDB 8 imports on compatible runners
* docs(web): add Railway and Vercel migration pages
* feat(dashboard): add shared dotenv text editing and top add action
* fix(dashboard): wrap text editor actions on narrow screens
* perf: reuse Docker builders and parallelize independent Compose work
* test: exercise declared dependency gates on the isolated Docker host
* fix: preserve dependency ownership and native cache maintenance
* fix: drain dependency readiness failures through the shared task barrier
* test: align server recovery expectations with source scan recovery
* fix: retain released dependency providers during publication recovery
* Keep route verification and bound parallel deployment work safely
* Send scoped cancellation confirmations through the customer email queue
* Offer help without treating one canceled subscription as account churn
* Invite cancellation feedback and offer direct support
* Preserve native Docker dependency cache across source changes
* Keep runtime dependencies ahead of changing API source
* Split independent Docker regression suites across CI jobs
* Use fresh connections for routing configuration probes
* Show published deployments while final startup verification runs
* Complete verification translations and align test types
* fix(edge): serve a static site's 404.html for missing paths
* fix(routing): make static SPA fallback explicit and preserve defaults
* test(routing): update static fallback checks and run HTTP coverage
* fix(i18n): complete inbound alias guidance across locales
* test(monitoring): isolate the session in stream fixtures
---------
Co-authored-by: Hydra <abdelhamedmo59@gmail.com>
* Add OpenTelemetry Collector to the apps catalog
Adds otel-collector as a one-click app template (docker-compose kind,
category: analytics), alongside Grafana and the other observability
apps. Uses the upstream otel/opentelemetry-collector-contrib image
unmodified — its baked-in default config already stands up OTLP gRPC
(4317) and HTTP (4318) receivers plus a debug exporter, so no custom
command/config override is needed to get a usable collector running.
Also wires up brand-mark resolution:
- AppLogo.tsx: catalog logo "otel-collector" → simpleicons "opentelemetry"
- ServiceIcon.tsx: image name → same brand mark, for services created
from a raw compose file rather than the catalog (both
"opentelemetry-collector-contrib" and "otel-collector" match)
catalog.json regenerated from apps/catalog/*.json per the drift test in
apps/catalog.test.ts (gen-catalog.ts requires bun, unavailable in this
environment — reproduced its exact merge/sort logic with a plain node
script; verified the new entry lands alphabetically and the rest of the
file is a no-op diff).
* feat: add Beszel to app catalog
* feat(catalog): add Prometheus
One-click Prometheus (prom/prometheus:v3.15.1) for the monitoring stack
requested in #1432. Metrics and config live in named volumes, so scrape
targets added to /etc/prometheus/prometheus.yml survive restarts and
redeploys. Prometheus has no login, so the connection notes point users to
domain password protection.
Refs #1432
* fix(ui): add the Prometheus app logo
The dashboard's APP_LOGO map needs an entry for every catalog app
(app-logo.test.ts). Use the simpleicons prometheus mark, like Grafana.
Refs #1432
* feat(catalog): add Loki
One-click Loki (grafana/loki:3.7.9) for the monitoring stack requested in
#1432. Logs live in a named volume and are kept for 31 days through the
compactor's retention flags. The image is distroless, so there is no shell
healthcheck and the flags are passed with commandArgv. Loki has no login,
so the connection notes point users to password protection.
Refs #1432
* fix(web): ship the Loki logo on the website too
Vendored app logos must be byte-identical in the dashboard and website
public folders (scripts/app-marketplace.test.ts).
Refs #1432
* feat(catalog): add VictoriaMetrics
One-click VictoriaMetrics (victoriametrics/victoria-metrics:v1.154.1) for the
monitoring stack requested in #1432. It is protected by default: basic auth
with username admin and an auto-generated password, passed through
-envflag.enable so it never appears in the command line. Metrics are kept
for one year in a named volume; /health stays open for the healthcheck.
Refs #1432
* feat(catalog): add standalone pgAdmin4 app
Adds pgAdmin4 as its own one-click catalog app, separate from the existing
PostgreSQL + pgAdmin bundle (postgresql.json). This one ships with no
database of its own — it's for administering any reachable PostgreSQL
server, including another Openship-deployed database's private connection,
a managed cloud database, or anything else on the network.
Reuses the exact service shape already proven by postgresql.json's pgadmin
service (same image/version, port, healthcheck): dpage/pgadmin4:9.18,
PGADMIN_DEFAULT_EMAIL + PGADMIN_DEFAULT_PASSWORD (the officially documented,
fully deterministic setup — no random/log-only credential to work around),
surfaced directly in the connection card.
Also maps the pgAdmin4 brand mark in packages/ui/src/AppLogo.tsx: simpleicons
carries no pgAdmin glyph (cdn.simpleicons.org/pgadmin4 404s), so it resolves
to the project's GitHub org avatar, the same pattern already used for
Ollama, vLLM, and Miniflux.
Verified against the real image (dpage/pgadmin4:9.18): booted it standalone
with the same env vars, confirmed the /misc/ping healthcheck responds once
gunicorn finishes initializing (needs the ~60s startPeriod already used by
postgresql.json).
Verified: bun scripts/gen-catalog.ts + bunx vitest run src/apps/catalog.test.ts (46/46 passing),
bun run --cwd packages/ui lint (tsc clean).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
* feat(catalog): add Listmonk app
Adds Listmonk (newsletter/mailing-list manager) as a one-click catalog app:
a private Postgres instance plus the Listmonk service, non-interactive
install + Super Admin creation on first boot via the officially documented
LISTMONK_ADMIN_USER/LISTMONK_ADMIN_PASSWORD env vars, surfaced directly in
the connection card.
commandArgv runs "./listmonk --install --idempotent --yes && exec
./listmonk" — install is a no-op on redeploy (idempotent flag), so the
same command is safe on every boot, no separate prepare step needed.
Verified against the real image (listmonk/listmonk:v6.2.0), not just docs:
- Ran the exact install+serve command against a live Postgres, confirmed
the superadmin user is created non-interactively ("creating superadmin
user 'admin'" in the log).
- The image's default app.address is localhost:9000 (unreachable from
outside the container) — set LISTMONK_app__address=0.0.0.0:9000, confirmed
it then actually listens and responds.
- Logged in via POST /admin/login with the exact generated password,
confirmed an authenticated session (302 + session cookie, 200 on an
authenticated /api/settings call).
- Confirmed /health returns 200 for the healthcheck.
- bun scripts/gen-catalog.ts + bunx vitest run src/apps/catalog.test.ts: 46/46 passing
(added minEngine: 0.6.6, required by the schema whenever commandArgv is used).
Continues M3 (Tier B: app + one DB), first of this batch.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
* fix(apps): declare a host port so the app can't collide with others
Without a ports entry the host port equals the container port, so a second
app on the same port fails with 'port is already allocated'.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix(apps): declare a host port so the app can't collide with others
Without a ports entry the host port equals the container port, so a second
app on the same port fails with 'port is already allocated'.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix(apps): use a unique host port, not the container port
In port mode the host port is taken from the ports entry, so 'N:N' still
collides with whatever already holds that port (80, 3000, ...). Match the
other catalog apps and publish on a distinct host port.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix(apps): use a unique host port, not the container port
In port mode the host port is taken from the ports entry, so 'N:N' still
collides with whatever already holds that port (80, 3000, ...). Match the
other catalog apps and publish on a distinct host port.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* feat(catalog): add Appwrite and Alertmanager with verified community recipes
---------
Co-authored-by: Giovanni Martins <giovannidealmeidamartins@gmail.com>
Co-authored-by: anshori <anshoriacc@gmail.com>
Co-authored-by: Asad Khan <55049186+AsadKhanAb17@users.noreply.github.com>
Co-authored-by: alkomy <alkomy@icloud.com>
Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
* feat(cluster): admit and apply project Kubernetes manifests
First step toward #1039: the engine for deploying user-supplied Kubernetes
manifests into a k3s cluster project, with no UI or deploy wiring yet.
- parseProjectManifests: multi-document YAML, size and object-count limits,
errors that name the failing document.
- admitProjectManifests: an allowlist of namespaced kinds (ConfigMap, Secret,
ClusterIP Service, Deployment, Job, CronJob). Refuses cluster-scoped kinds,
other namespaces, ownerReferences, finalizers, reserved labels, NodePort,
host networking/PID/IPC, hostPath, PVCs, privileged containers, hostPort and
non-default service accounts. Pins objects to the project namespace, stamps
ownership labels and a content hash, and disables token automount.
- applyProjectManifests: create, skip unchanged, replace changed objects it
owns (keeping a Service's cluster IP), and prune manifest objects that are
no longer declared. Openship's own app objects are never replaced.
- Project deletion accepts owned ConfigMap, Job and CronJob objects.
Refs #1039
* fix: preflight manifest changes and protect generated ownership
* fix(cluster): keep manifest deployments out of native release sweeps
---------
Co-authored-by: Hydra <abdelhamedmo59@gmail.com>
Cover full published-stack upgrades, retained data and signed sessions, cold restart and fresh installation. Reuse runtime preflight in advisory views and expose source-redeploy prerequisites. Refs #1461 and #1462.
* feat: add runtime security advisories and annual Cloud billing
* fix(updates): show runtime advisories in the global update center
* fix(updates): synchronize advisory consent across global views
* refactor(updates): reuse normal refresh and environment flow
* fix(security): pin patched Node and Bun runtimes across releases
* fix(build): pass bootstrap selection independently of eval arguments
* test(build): expect the patched default Bun image in detection
* docs: prepare 0.9.4 changelog since 0.9.3
Merge the updated Swarm discovery parent and regenerate MCP references. Match the wizard to the existing self-hosted controller gate so hosted BYOC cannot stage unsupported route passwords. Cover hosted BYOC, self-hosted servers, cloud targets, and cluster targets with the real editor.
Stage only independent services with verified spare target capacity. Keep
incumbents untouched until readiness, complete routing, and the durable
release outcome. Restore routes before cancellation cleanup and preserve
both workloads when restoration cannot be verified.
Co-authored-by: Daniel Greer <13854262+greerso@users.noreply.github.com>