Repository navigation
Conversation
…ontainers Abort failover when the chosen target does not answer its SSH port, refuse automatic failovers within FAILOVER_MIN_INTERVAL_MS (default 10m), allow disabling the monitor with FAILOVER_DISABLED, and remove the previous deployment's containers from the old server behind a 30s cap so a dead host cannot hang the failover.
Remote builds cloned the repo and ran `railpack build .` without ever consulting the project's sourceDir or projectType, so any project whose code lives in a subfolder failed with "Railpack could not determine how to build the app" while the same project deployed fine locally. Send the local railpack-config-utils.ts source to the target host, write it into the clone through a quoted heredoc, and run it there with bun, which is installed unzip-free via python3 when the host has neither bun nor unzip. Remote failures now read stdout before stderr, so failureReason no longer reports git's "Cloning into '.'..." instead of the real error.
…eployment's server ingressSite (the route writer for cross-server projects behind the local ingress) never emitted CADDY_ACCESS_LOG_BLOCK, so project requests were never access-logged and request-logs/metrics stayed empty. Runtime logs ran 'docker logs' against the local node for every deployment (the SSE stream used a raw spawn, bypassing ssh targeting), returning [] for anything on a remote server; both handlers now resolve the deployment's server behind orchestrator/runtime-logs.ts.
…database hosts Close out the open rows from artifacts/verify-dequel/BUGS.md (005-018, 027, 028, 030-033, 039, 040), live-verified on the primary host. BUG-027: cancelling a deployment now kills the build's whole process group (detached local spawns with pgid tracking, DEQUEL_PGID echoed by the remote script and parsed on abort), and the cancel handler reports the abort instead of a generic failure. BUG-039: pam-auth mounts host /etc as a directory and copies passwd/shadow/group into the container in place every 2s, so useradd/chpasswd/usermod become visible to PAM immediately — file binds froze the mount-time inode so logins kept failing until a restart. BUG-040: Caddy now provisions real Let's Encrypt certificates for db-* hostnames (site route files database-<host>.caddy written on create, patch, and delete trigger auto-HTTPS), and the gateway serves those certs from the shared caddy-data volume (mtime-cached, SAN and expiry checked, self-signed fallback kept). Live-verified: openssl -verify_return_error returns 0 for all three public databases and the node pg driver's verify-full semantics now connect out of the box. BUG-016: the credentials endpoint probes external reachability and returns a warning the dashboard surfaces when the endpoint is down. Also extract authMiddleware into its own module, add lazy repo imports and orchestrator mocks so bun test runs green again (440 pass, 1 pre-existing DiagRunMachine failure), and correct the database TLS docs note to describe the new certificate path.
hosts for connections Wire Caddy certificate detection into connection strings and resolve direct database endpoints from their assigned server. Also begins refactoring Railpack process cancellation.
tunables Persist a generated encryption key during installation and migrate existing encrypted secrets on startup. Configure GitHub integration through the dashboard instead of config seeding.
initialization
Validate production secrets and scaling ranges, improve cleanup and process handling, and fix authentication, SSH, gateway, and webhook edge cases. Update related docs and dashboard behavior.
fix: fix bugs
chore: update dequel documentation pages
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Lftobs
marked this pull request as ready for review
October 11, 2026 19:07
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.