ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #ghost
Ghost’s HTTP server treats each request as cancelable when the underlying socket emits a 'close' or 'end' event, allowing middleware to abort processing early. The Ghost CLI’s ghost stop command initiates a graceful shutdown that respects the server.shutdownTimeout setting (default 5000 ms) introduced in Ghost 5.0. However, the Admin API does not yet honor t
Error context Ghost logs an ENOENT error when it tries to read an image from the content/images directory. The stack trace appears to come from the storage adapter layer (ghost-storage-adapter-base), which sits between Ghost core and either the local filesystem or an external service such as S3. The goal is to determine whether the failure means the file is
The Ghost publishing platform builds absolute URLs for stylesheets, scripts, images and feeds from the `url` value in its configuration. When the same configuration works on a developer’s machine but the live site shows broken styling and missing images, the symptom is that browsers request those resources from an address that does not match the public domai
Distributed Content Delivery and Cache Synchronization Ghost CMS utilizes an internal caching layer to minimize database queries and improve frontend performance. In a standard single-node deployment, content updates in the admin panel typically trigger a cache invalidation that ensures the frontend reflects changes immediately. When scaling Ghost horizontal
Goal Upgrade a lightweight Ghost CMS instance while keeping the site online. Constraints Single‑node deployment on Linux, default SQLite, and a process manager such as systemd or PM2. Unresolved Decision Both documented methods claim zero‑downtime, but the real impact on latency and user experience is unclear. Questions Will the brief pause introduced by Gho
Ghost v5 exposes a configurable timeout for inbound HTTP request parsing and a gracefulShutdownTimeout for process termination on SIGTERM/SIGINT. The documented settings affect server close behavior, but the interaction with long-running Admin API operations and outbound webhook deliveries is not fully defined. The Admin API does not expose a standard AbortC
Self-hosted Ghost does not manage DNS records or TLS certificates. Domain resolution must complete via A, AAAA or CNAME records before requests reach the host, and certificate validation is handled outside core, typically by a reverse proxy in front of the Node.js process. The operator must decide how certificate renewal is performed and how the proxy is rel
Recovery Strategy Selection When restoring a self-hosted Ghost instance, there is a trade-off between using the built-in JSON export/import feature and performing a full MySQL/MariaDB database restoration combined with a content directory migration. Constraint Analysis The JSON export provides a portable, version-agnostic method for migrating posts, pages, a
Goal: achieve immediate, selective removal of the cached HTML for a specific post when its content is updated via the Ghost admin API, avoiding a full cache flush. Constraint: Ghost’s file‑system cache under content/data/cache/ is only invalidated by time‑to‑live expiration or by the ghost cache clear command, which deletes the entire cache directory and can
docker