Repository navigation
[Script request]: OpenShip #18708
Unanswered
shrijayan
asked this question in
Request script
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Application Name
OpenShip
Official Website
https://openship.io
Source Repository
https://github.com/oblien/openship
Repository Stars
15,283
Minimum Adoption Requirement
Description
OpenShip is an Apache-2.0 self-hosted deployment platform in the Heroku/Vercel/Coolify class. It builds and runs apps from a Git repo or a local folder as plain Docker containers, next to managed Postgres/Redis services, and fronts them with a bundled OpenResty edge that handles domains and Let's Encrypt TLS. Also included: scheduled jobs, backups, release rollbacks, per-route traffic rules, a mail server, and an MCP server so AI clients can drive deploys. TypeScript monorepo — Next.js dashboard, API, CLI, and an Electron desktop app. 15.3k stars, 1.4k forks, 8 releases since 24 October (v0.9.12 on 2026-11-12).
Why should this be added?
The repo already has this category covered —
ct/dokploy.shwithtools/addon/dokploy.sh, andtools/addon/coolify.sh— so the Docker-in-LXC deploy-platform pattern exists and OpenShip slots into it without inventing anything new.What makes it worth adding rather than "another PaaS": it can adopt containers already running on the box instead of rebuilding them, it keeps build/env/domain/service config in an
openship.jsonin the repo, and deleting a project removes only its record — the containers and data keep serving. For a homelab that is the difference between trying it and committing to it.It is also large and current: 15.3k stars, 8 months old, pushed today. No existing script and no existing request — checked both.
Installation Notes
openship updefaults to the Compose stack there. Services:postgres:16-alpine(private :5432), Redis (private :6379),api(:4000),dashboard(:3001), and an OpenRestyedgeon :80/:443 using host networking. Images pull fromghcr.io/oblien/*.curl -fsSL https://get.openship.io | shdrops a checksum-verified CLI into~/.openship(/root/.openshipas root) and vendors Node 22 when the system Node is older. Thenopenship up.OPENSHIP_ADMIN_PASSWORD=... openship up --non-interactive --admin-email ... --admin-name ... --domain-kind none|byo|custom --edge migrate|takeover|cancel, plus--dry-run.OPENSHIP_BIND_ADDR(e.g.0.0.0.0) andOPENSHIP_PUBLIC_URL, or login fails with403 ORIGIN_REJECTED. Worth setting in the script, since an LXC is normally reached over the LAN.apimounts the host Docker socket (Docker-out-of-Docker), so the container needs to be privileged withnesting=1/keyctl=1— the same shape asct/dokploy.sh.openship upgenerates an SSH key, authorizes it for the invoking user, and reaches the host overhost.docker.internal. Inside an LXC "the host" is the container itself, so this needssshdin the LXC (community-scripts images don't ship it) or--no-host-control, which drops "This Server" as a deploy target. This is the one decision the script has to make explicitly.initdbEPERM failure on LXC/OpenVZ hosts and recommends a native ext4/xfs Docker data-root. Keeping Docker's default data-root on the container's ext4 rootfs avoids it; a bind-mounted ZFS/NFS path would not.openship uninstallremoves the stack but deliberately leaves deployed app containers running.Due Diligence
Justification for an exception
No response
All reactions