[pull] master from caprover:master#283
Open
pull[bot] wants to merge 441 commits intonext-stack:masterfrom
Open
[pull] master from caprover:master#283pull[bot] wants to merge 441 commits intonext-stack:masterfrom
pull[bot] wants to merge 441 commits intonext-stack:masterfrom
Conversation
- Added getCertbotCertCommand method in CertbotManager for dynamic cert commands - Refactored enableSsl method to use the new dynamic cert command generator - Introduced certbotCertCommand configuration in CaptainConstants for customizable commands
- Extracted certificate success logic into isCertCommandSuccess function - Ensured compatibility with previous certbot success messages
- Removed a redundant comma in function arguments - Added a space before function declaration for consistency
mod: dockerignore
- Introduced CertbotCertCommandRule for dynamic command generation - Refactored CertbotManager to utilize a CertCommandGenerator - Added new tests for the CertCommandGenerator logic
Optimize Dockerfile to Reduce Production Image Size
This reverts commit fb819ec.
API skeleton added for automated cleanup
Added OpenStack Heat template for deploying single-instance CapRover
Allow numbers in project name, fix #2130
[HOTFIX] Updated Docker API version
Release backmerge
Gzip config
Add support for new ANONYMIZE_IP env in goAccess
The existing POST /update/ replaces all fields — omitted fields are
reset to defaults (e.g. envVars becomes [], instanceCount becomes 0).
This makes simple operations like scaling dangerous: sending only
{appName, instanceCount} wipes all environment variables.
The new PATCH /update/ endpoint fetches the existing app definition
and merges only the explicitly provided fields. Omitted fields retain
their current values.
Example — scale without touching env vars:
PATCH /api/v2/user/apps/appDefinitions/update/
{"appName": "my-app", "instanceCount": 1}
The POST endpoint is unchanged — full backward compatibility.
Add PATCH endpoint for partial app definition updates
Backup tar files currently use a filename that only encodes a
timestamp and the leader's IP, e.g.
caprover-backup-2026_04_10-19_30_00-1744312200000-ip-1_2_3_4.tar
When you run several CapRover instances behind a NAT or with
similar IPs, that filename is not enough to tell the backups apart
after downloading them.
This appends the swarm leader's hostname to the existing filename:
caprover-backup-...-ip-1_2_3_4-host-captain-prod.tar
The hostname is sanitized to a portable charset ([A-Za-z0-9._-]) so
it is safe in filesystems and HTTP Content-Disposition headers, and
the segment is omitted entirely when the leader has no hostname, so
existing single-node setups see no change beyond an additional
suffix when one is available.
The sanitization step is exposed as a small static helper
(`BackupManager.sanitizeHostnameForFilename`) so it can be unit
tested in isolation. Top-level cleanup hooks in the existing test
file are now gated on `process.env.CI`, matching how the
integration tests in the same file are gated, so the new pure
helper tests can run on a developer workstation.
Closes #1257
…hostname Append leader hostname to backup filename
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
20 participants
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.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )