Issues/add missing tutorials - #50
Conversation
… SSH keygen guides Builds on the version-badge idea from @cokerrd (#48): - installation: give the badge real alt text and wrap it in a link to releases/latest; allow img.shields.io in the production CSP (img-src) so the badge actually renders in prod instead of being blocked - object-storage: add an s3cmd config and command reference to S3 API Usage - compute: add an SSH key generation section to Connect With SSH
Bring the French installation, s3-usage, and connect-ssh pages into parity with their English source. Code blocks and commands stay identical to English, links use the /fr/ prefix, and the version badge alt text is translated. Generated with the Codex CLI, then reviewed for code-block fidelity, heading parity, link prefixes, and build validity.
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
📝 WalkthroughWalkthroughUpdated English and French CLI, SSH, S3, changelog, and marketplace documentation. Marketplace pages now describe first-boot deployment workflows, operations, credentials, and network security. The marketplace catalog, CSP policy, and package overrides were also updated. ChangesDocumentation and deployment updates
Estimated code review effort: 5 (Critical) | ~120 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (1 warning, 1 inconclusive)
✅ Passed checks (3 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@deploy/caddy/prd.Caddyfile`:
- Line 73: Update the Content-Security-Policy directive in the production Caddy
configuration to remove analytics.zsoftly.ca from script-src while preserving
ds360.co and cdn.pixel.zymplify.com. Leave analytics.zsoftly.ca in any other
required CSP directive, such as connect-src, and do not change the existing
unsafe-inline handling.
In `@src/content/docs/public-cloud/storage/object-storage/s3-usage.mdx`:
- Around line 262-263: Update the English s3cmd introduction in
src/content/docs/public-cloud/storage/object-storage/s3-usage.mdx:262-263 to say
“S3-compatible storage” instead of “S3 storage.” Apply the corresponding wording
change in
src/content/docs/fr/public-cloud/storage/object-storage/s3-usage.mdx:266-267
from “stockage S3” to “stockage compatible S3.”
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: ba0b56a0-88c5-49af-82e3-457a81ae530e
📒 Files selected for processing (7)
deploy/caddy/prd.Caddyfilesrc/content/docs/fr/public-cloud/cli/installation.mdsrc/content/docs/fr/public-cloud/compute/connect-ssh.mdsrc/content/docs/fr/public-cloud/storage/object-storage/s3-usage.mdxsrc/content/docs/public-cloud/cli/installation.mdsrc/content/docs/public-cloud/compute/connect-ssh.mdsrc/content/docs/public-cloud/storage/object-storage/s3-usage.mdx
- Rancher: Added software version details, environment variables, and improved deployment instructions. - SeaweedFS: Updated software version, added environment variables, and clarified deployment steps. - Uptime Kuma: Revised software version, added environment variables, and improved setup instructions. - WG-Easy: Updated software version, added environment variables, and clarified deployment steps. - Wiki.js: Revised software version, added environment variables, and improved setup instructions. - Zammad: Updated software version, added environment variables, and clarified deployment steps. - S3 Usage: Minor clarification in the s3cmd section for better understanding.
There was a problem hiding this comment.
Actionable comments posted: 10
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
src/content/docs/fr/public-cloud/storage/object-storage/s3-usage.mdx (1)
278-280: 📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick winRemove the vendor-specific reference from this public page.
ZSoftlymakes the Public Cloud documentation non-neutral and exposes an internal implementation detail. Use neutral wording such as “requis par le service”.Proposed wording
- force l'adressage path-style exigé par ZSoftly. + force l'adressage path-style requis par le service.As per coding guidelines, Public Cloud (
ZCP) pages must be vendor-neutral and must not mention internal backends.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@src/content/docs/fr/public-cloud/storage/object-storage/s3-usage.mdx` around lines 278 - 280, Update the object-storage configuration guidance to remove the vendor-specific “ZSoftly” reference and replace it with neutral wording such as “requis par le service,” while preserving the path-style addressing instruction and Ottawa example.Source: Coding guidelines
src/content/docs/public-cloud/marketplace/index.md (1)
20-21: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winCorrect the marketplace category count.
The page contains nine marketplace categories, or ten sections if “Most Popular” is counted—not 11. Update the statistic or add the missing category.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@src/content/docs/public-cloud/marketplace/index.md` around lines 20 - 21, Update the marketplace statistic in the category-count markup from 11 to the accurate count: use 9 for marketplace categories, or 10 only if “Most Popular” is included. Alternatively, add the missing category so the displayed count of 11 is accurate.
🧹 Nitpick comments (1)
src/content/docs/public-cloud/marketplace/artifactory.md (1)
19-24: 🔒 Security & Privacy | 🔵 Trivial | ⚡ Quick winClarify the credential flow for these marketplace apps. Across Artifactory, ClickHouse, Nginx Proxy Manager, and NocoDB, the env vars are presented as optional/generated secrets while the onboarding steps still hardcode defaults or a first-run flow. Spell out when blank fields generate credentials, when supplied values override defaults, and what users should enter to log in.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@src/content/docs/public-cloud/marketplace/artifactory.md` around lines 19 - 24, Clarify the credential flow across all listed marketplace documentation: in src/content/docs/public-cloud/marketplace/artifactory.md lines 19-24 and 69-76, clickhouse.md lines 18-26 and 55-70, nginx-proxy-manager.md lines 16-24 and 57-64, and nocodb.md lines 16-24 and 49-65, state that blank credential fields generate secure values, supplied values override defaults, and identify exactly which generated or supplied credentials users must use to log in instead of hardcoded or ambiguous onboarding instructions.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/content/docs/fr/changelog/index.md`:
- Around line 54-55: Update the French changelog text by replacing the straight
apostrophes in “l'identifiant” and “d'une” with typographic apostrophes,
yielding “l’identifiant” and “d’une”.
In `@src/content/docs/public-cloud/marketplace/apache-kafka.md`:
- Around line 93-99: Update the SSH-tunnel procedure in the Kafka marketplace
documentation to include the exact server.properties edit that sets
advertised.listeners to localhost, followed by the required Kafka restart
command. Place these steps before the existing local ssh -L command so clients
receive the tunneled address after bootstrap.
In `@src/content/docs/public-cloud/marketplace/directus.md`:
- Around line 49-53: Update the curl health checks in
src/content/docs/public-cloud/marketplace/directus.md lines 49-53 and
src/content/docs/public-cloud/marketplace/gitea.md lines 48-51 to use curl’s
-fsS options, preserving their existing endpoints so HTTP 4xx/5xx responses
return failure exit codes.
In `@src/content/docs/public-cloud/marketplace/gitea.md`:
- Around line 67-70: Update the administrator credentials table in the Gitea
documentation so the Username value reflects the configurable GITEA_ADMIN_USER
setting: reference /etc/gitea/credentials.txt as the source, or explicitly
identify zadmin as only the default. Keep the Password entry unchanged.
In `@src/content/docs/public-cloud/marketplace/mattermost.md`:
- Around line 23-27: Update the Mattermost access instructions to use the
configured MM_SERVICESETTINGS_SITEURL or DOMAIN hostname when present, including
the required DNS and TLS setup; clarify that http://<your-vm-ip> applies only
when those settings are unset or default.
In `@src/content/docs/public-cloud/marketplace/pelican-panel.md`:
- Around line 63-70: Make the scheduler setup in the “Enable scheduled tasks and
the queue worker” section idempotent by checking for the exact Pelican cron
entry before adding it, or by replacing it with a managed systemd timer.
Preserve enabling and starting pelican-queue, and ensure repeated installer runs
create only one scheduler definition.
In `@src/content/docs/public-cloud/marketplace/qdrant.md`:
- Around line 11-15: Replace every GFM pipe table with an equivalent raw HTML
table in the affected marketplace documents: qdrant.md lines 11-15 (software,
credentials, and paths), rabbitmq.md lines 12-15 (software,
environment-variable, credentials, and paths), rancher.md lines 12-16 (software,
environment-variable, credentials, and paths), seaweedfs.md lines 11-14
(software, credentials, endpoint, and paths), uptime-kuma.md lines 11-15
(software and paths), wg-easy.md lines 12-15 (software, environment-variable,
and paths), wikijs.md lines 12-17 (software, environment-variable, and paths),
and zammad.md lines 12-19 (software and paths). Preserve each table’s headings,
cell values, and ordering while using raw HTML table markup throughout.
In `@src/content/docs/public-cloud/marketplace/rancher.md`:
- Around line 25-26: Update the Rancher access instructions to use
https://<RANCHER_HOSTNAME> whenever RANCHER_HOSTNAME is configured instead of an
IP-based URL, and explicitly state that the hostname must resolve through DNS
before access. Keep the existing BOOTSTRAP_PASSWORD guidance unchanged.
In `@src/content/docs/public-cloud/marketplace/seaweedfs.md`:
- Around line 26-27: Update the public-cloud SeaweedFS page’s object-storage
terminology throughout the referenced sections, including the first-boot
description, to use vendor-neutral “S3-compatible” wording. Replace “S3
credentials,” “S3 API,” “S3 credential environment,” and equivalent references
with the corresponding S3-compatible terminology while preserving the documented
setup behavior.
In `@src/content/docs/public-cloud/marketplace/uptime-kuma.md`:
- Around line 87-94: Update the direct-access guidance near the Docker Compose
port mapping to stop recommending the unrestricted `3001:3001` binding with only
a UFW rule. Keep `127.0.0.1:3001:3001` and direct users to the SSH tunnel or
reverse proxy, or document enforcement through `DOCKER-USER` or an equivalent
host-firewall chain.
---
Outside diff comments:
In `@src/content/docs/fr/public-cloud/storage/object-storage/s3-usage.mdx`:
- Around line 278-280: Update the object-storage configuration guidance to
remove the vendor-specific “ZSoftly” reference and replace it with neutral
wording such as “requis par le service,” while preserving the path-style
addressing instruction and Ottawa example.
In `@src/content/docs/public-cloud/marketplace/index.md`:
- Around line 20-21: Update the marketplace statistic in the category-count
markup from 11 to the accurate count: use 9 for marketplace categories, or 10
only if “Most Popular” is included. Alternatively, add the missing category so
the displayed count of 11 is accurate.
---
Nitpick comments:
In `@src/content/docs/public-cloud/marketplace/artifactory.md`:
- Around line 19-24: Clarify the credential flow across all listed marketplace
documentation: in src/content/docs/public-cloud/marketplace/artifactory.md lines
19-24 and 69-76, clickhouse.md lines 18-26 and 55-70, nginx-proxy-manager.md
lines 16-24 and 57-64, and nocodb.md lines 16-24 and 49-65, state that blank
credential fields generate secure values, supplied values override defaults, and
identify exactly which generated or supplied credentials users must use to log
in instead of hardcoded or ambiguous onboarding instructions.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 9cfb72e5-a436-42bb-9686-70ec41ab82f6
📒 Files selected for processing (36)
deploy/caddy/prd.Caddyfilesrc/content/docs/changelog/index.mdsrc/content/docs/fr/changelog/index.mdsrc/content/docs/fr/public-cloud/storage/object-storage/s3-usage.mdxsrc/content/docs/public-cloud/marketplace/apache-kafka.mdsrc/content/docs/public-cloud/marketplace/apache-tomcat.mdsrc/content/docs/public-cloud/marketplace/artifactory.mdsrc/content/docs/public-cloud/marketplace/bagisto.mdsrc/content/docs/public-cloud/marketplace/beszel.mdsrc/content/docs/public-cloud/marketplace/clickhouse.mdsrc/content/docs/public-cloud/marketplace/directus.mdsrc/content/docs/public-cloud/marketplace/erpnext.mdsrc/content/docs/public-cloud/marketplace/gatus.mdsrc/content/docs/public-cloud/marketplace/gitea.mdsrc/content/docs/public-cloud/marketplace/haproxy.mdsrc/content/docs/public-cloud/marketplace/harbor.mdsrc/content/docs/public-cloud/marketplace/index.mdsrc/content/docs/public-cloud/marketplace/mattermost.mdsrc/content/docs/public-cloud/marketplace/medusa.mdsrc/content/docs/public-cloud/marketplace/mongodb.mdsrc/content/docs/public-cloud/marketplace/neo4j.mdsrc/content/docs/public-cloud/marketplace/nexus.mdsrc/content/docs/public-cloud/marketplace/nginx-proxy-manager.mdsrc/content/docs/public-cloud/marketplace/nginx.mdsrc/content/docs/public-cloud/marketplace/nocodb.mdsrc/content/docs/public-cloud/marketplace/pelican-panel.mdsrc/content/docs/public-cloud/marketplace/pterodactyl.mdsrc/content/docs/public-cloud/marketplace/qdrant.mdsrc/content/docs/public-cloud/marketplace/rabbitmq.mdsrc/content/docs/public-cloud/marketplace/rancher.mdsrc/content/docs/public-cloud/marketplace/seaweedfs.mdsrc/content/docs/public-cloud/marketplace/uptime-kuma.mdsrc/content/docs/public-cloud/marketplace/wg-easy.mdsrc/content/docs/public-cloud/marketplace/wikijs.mdsrc/content/docs/public-cloud/marketplace/zammad.mdsrc/content/docs/public-cloud/storage/object-storage/s3-usage.mdx
🚧 Files skipped from review as they are similar to previous changes (2)
- deploy/caddy/prd.Caddyfile
- src/content/docs/public-cloud/storage/object-storage/s3-usage.mdx
…ncluding WG-Easy, Wiki.js, Zammad, and others. Updates include improved language clarity, corrected technical details, and enhanced security recommendations. Adjusted environment variable descriptions and deployment instructions for better user guidance. Fixed minor typos and formatting issues across multiple files.
There was a problem hiding this comment.
Actionable comments posted: 8
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
src/content/docs/fr/public-cloud/storage/object-storage/s3-usage.mdx (2)
273-280: 🔒 Security & Privacy | 🟠 Major | ⚡ Quick winRemove internal endpoint names from the public guide.
These concrete
zcp.zsoftly.cahostnames expose internal infrastructure and make the public-cloud documentation vendor-specific. Replace them with a neutral S3-compatible endpoint placeholder and direct users to the authoritative regional endpoint source.As per coding guidelines, Public Cloud (
ZCP) pages must be vendor-neutral: do not mention internal backends, and describe object storage only asS3-compatible.Suggested adjustment
-host_base = objects.yul.zcp.zsoftly.ca -host_bucket = objects.yul.zcp.zsoftly.ca +host_base = <s3-compatible-endpoint> +host_bucket = <s3-compatible-endpoint> ... -`objects.yow.zcp.zsoftly.ca`. +the S3-compatible endpoint provided for your region.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@src/content/docs/fr/public-cloud/storage/object-storage/s3-usage.mdx` around lines 273 - 280, Replace the concrete zcp.zsoftly.ca hostnames in the S3 configuration example with a neutral S3-compatible endpoint placeholder, preserving the path-style host_base and host_bucket guidance. Remove the vendor-specific Ottawa example and direct readers to the authoritative source for their regional S3-compatible endpoint.Source: Coding guidelines
269-276: 🔒 Security & Privacy | 🟠 Major | ⚡ Quick winRestrict permissions on
~/.s3cfg.This file contains
secret_key; add an explicitchmod 600 ~/.s3cfgstep after creation so the credentials are not readable by other local users when the default umask is permissive.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@src/content/docs/fr/public-cloud/storage/object-storage/s3-usage.mdx` around lines 269 - 276, Add an explicit chmod 600 ~/.s3cfg command immediately after creating the s3cfg configuration in the documented setup flow, ensuring the file containing secret_key is readable and writable only by its owner.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/content/docs/fr/public-cloud/marketplace/artifactory.md`:
- Around line 18-25: Update the login instructions in
src/content/docs/fr/public-cloud/marketplace/artifactory.md (Lines 71–79) to use
the configured or generated administrator password from
ARTIFACTORY_ADMIN_PASSWORD. In
src/content/docs/fr/public-cloud/marketplace/nginx-proxy-manager.md (Lines
58–65), distinguish default credentials from configured or generated marketplace
values. In src/content/docs/fr/public-cloud/marketplace/clickhouse.md (Lines
55–72), reference the configured username instead of always using default.
In `@src/content/docs/fr/public-cloud/marketplace/erpnext.md`:
- Around line 112-120: Update the SSH tunnel sections to remove public UFW
access before tunneling: in
src/content/docs/fr/public-cloud/marketplace/erpnext.md:112-120 remove the 8080
rule; gatus.md:89-97 remove 8080; gitea.md:105-113 remove 3000; haproxy.md:87-95
remove 80; harbor.md:109-117 remove 80 and document removing 443 when enabled;
mattermost.md:105-113 remove 80; medusa.md:102-110 remove 80; neo4j.md:106-114
remove 7474 and 7687; and nexus.md:105-113 remove 8081. Place the relevant ufw
delete allow commands before each tunnel command.
In `@src/content/docs/fr/public-cloud/marketplace/gitea.md`:
- Around line 5-7: Update the introductory description of Gitea so it no longer
presents the CI runner as part of the single Gitea binary. Clarify that Gitea
Actions is server-side and that act_runner/Gitea Runner is a separate program
requiring independent installation and registration, or explicitly document its
provisioning in the Marketplace image.
In `@src/content/docs/fr/public-cloud/marketplace/mongodb.md`:
- Around line 61-63: Update the mongosh invocation in the MongoDB connection
instructions to avoid passing MONGO_PASS through argv; use mongosh’s interactive
password prompt or another supported non-argv input method while preserving the
admin user and authenticationDatabase options.
- Around line 21-24: Update the MongoDB connection command to use the configured
username instead of hardcoding “admin”. Reuse the username exposed by
MONGO_INITDB_ROOT_USERNAME, or extract it from credentials.txt, and apply the
same correction to the additional referenced command.
In `@src/content/docs/fr/public-cloud/marketplace/pterodactyl.md`:
- Around line 94-119: Update the Sécurité section’s UFW examples to remove the
broad allow rules for Wings ports 8080 and 2022, then add commands permitting
each port only from a trusted IP or network. Keep the existing port 80
restriction and ensure the documented rules match the stated default firewall
configuration.
In `@src/content/docs/fr/public-cloud/marketplace/rabbitmq.md`:
- Around line 22-25: Update the marketplace documentation for
RABBITMQ_DEFAULT_USER so guest is not presented as a valid administrator value;
document the accepted-user constraint or explicitly describe the required
post-removal user creation flow, ensuring first boot always leaves a usable
configured administrator.
In `@src/content/docs/fr/public-cloud/marketplace/uptime-kuma.md`:
- Around line 89-93: Correct the firewall explanation in the Uptime Kuma
documentation: retain the 127.0.0.1:3001:3001 binding, but state that Docker’s
published-port rules bypass UFW, rather than attributing that behavior to the
DOCKER-USER chain. If recommending exposure of 3001:3001, direct users to
restrict it through DOCKER-USER or nftables.
---
Outside diff comments:
In `@src/content/docs/fr/public-cloud/storage/object-storage/s3-usage.mdx`:
- Around line 273-280: Replace the concrete zcp.zsoftly.ca hostnames in the S3
configuration example with a neutral S3-compatible endpoint placeholder,
preserving the path-style host_base and host_bucket guidance. Remove the
vendor-specific Ottawa example and direct readers to the authoritative source
for their regional S3-compatible endpoint.
- Around line 269-276: Add an explicit chmod 600 ~/.s3cfg command immediately
after creating the s3cfg configuration in the documented setup flow, ensuring
the file containing secret_key is readable and writable only by its owner.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 7773e1cc-c04f-430b-b1c9-2b182b07d3fa
📒 Files selected for processing (44)
src/content/docs/changelog/index.mdsrc/content/docs/fr/changelog/index.mdsrc/content/docs/fr/public-cloud/marketplace/apache-kafka.mdsrc/content/docs/fr/public-cloud/marketplace/apache-tomcat.mdsrc/content/docs/fr/public-cloud/marketplace/artifactory.mdsrc/content/docs/fr/public-cloud/marketplace/bagisto.mdsrc/content/docs/fr/public-cloud/marketplace/beszel.mdsrc/content/docs/fr/public-cloud/marketplace/clickhouse.mdsrc/content/docs/fr/public-cloud/marketplace/directus.mdsrc/content/docs/fr/public-cloud/marketplace/erpnext.mdsrc/content/docs/fr/public-cloud/marketplace/gatus.mdsrc/content/docs/fr/public-cloud/marketplace/gitea.mdsrc/content/docs/fr/public-cloud/marketplace/haproxy.mdsrc/content/docs/fr/public-cloud/marketplace/harbor.mdsrc/content/docs/fr/public-cloud/marketplace/index.mdsrc/content/docs/fr/public-cloud/marketplace/mattermost.mdsrc/content/docs/fr/public-cloud/marketplace/medusa.mdsrc/content/docs/fr/public-cloud/marketplace/mongodb.mdsrc/content/docs/fr/public-cloud/marketplace/neo4j.mdsrc/content/docs/fr/public-cloud/marketplace/nexus.mdsrc/content/docs/fr/public-cloud/marketplace/nginx-proxy-manager.mdsrc/content/docs/fr/public-cloud/marketplace/nginx.mdsrc/content/docs/fr/public-cloud/marketplace/nocodb.mdsrc/content/docs/fr/public-cloud/marketplace/pelican-panel.mdsrc/content/docs/fr/public-cloud/marketplace/pterodactyl.mdsrc/content/docs/fr/public-cloud/marketplace/qdrant.mdsrc/content/docs/fr/public-cloud/marketplace/rabbitmq.mdsrc/content/docs/fr/public-cloud/marketplace/rancher.mdsrc/content/docs/fr/public-cloud/marketplace/seaweedfs.mdsrc/content/docs/fr/public-cloud/marketplace/uptime-kuma.mdsrc/content/docs/fr/public-cloud/marketplace/wg-easy.mdsrc/content/docs/fr/public-cloud/marketplace/wikijs.mdsrc/content/docs/fr/public-cloud/marketplace/zammad.mdsrc/content/docs/fr/public-cloud/storage/object-storage/s3-usage.mdxsrc/content/docs/public-cloud/marketplace/apache-kafka.mdsrc/content/docs/public-cloud/marketplace/directus.mdsrc/content/docs/public-cloud/marketplace/gitea.mdsrc/content/docs/public-cloud/marketplace/index.mdsrc/content/docs/public-cloud/marketplace/mattermost.mdsrc/content/docs/public-cloud/marketplace/pelican-panel.mdsrc/content/docs/public-cloud/marketplace/rancher.mdsrc/content/docs/public-cloud/marketplace/seaweedfs.mdsrc/content/docs/public-cloud/marketplace/uptime-kuma.mdsrc/content/docs/public-cloud/storage/object-storage/s3-usage.mdx
🚧 Files skipped from review as they are similar to previous changes (8)
- src/content/docs/public-cloud/marketplace/apache-kafka.md
- src/content/docs/public-cloud/storage/object-storage/s3-usage.mdx
- src/content/docs/public-cloud/marketplace/directus.md
- src/content/docs/public-cloud/marketplace/uptime-kuma.md
- src/content/docs/public-cloud/marketplace/pelican-panel.md
- src/content/docs/public-cloud/marketplace/seaweedfs.md
- src/content/docs/public-cloud/marketplace/mattermost.md
- src/content/docs/public-cloud/marketplace/index.md
…security by closing default open ports and using SSH tunnels for access - Added instructions to close public ports for ERPNext, Gatus, Gitea, HAProxy, Harbor, Mattermost, Medusa, MongoDB, Neo4j, Nexus, Pterodactyl, RabbitMQ, and Uptime Kuma. - Updated MongoDB connection instructions to use the configured username instead of a hardcoded value. - Clarified the implications of Docker's port management in Uptime Kuma documentation. - Improved descriptions for RabbitMQ environment variables to clarify user roles and security measures. - Added permission restriction instructions for S3 configuration files.
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
src/content/docs/public-cloud/marketplace/mongodb.md (1)
42-44: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winTell users how to stop the live journal follow.
journalctl -u mongodb-first-boot.service -fkeeps running until interrupted, so add a Ctrl-C step after theREADYentry or replace it with a finite status/log command.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@src/content/docs/public-cloud/marketplace/mongodb.md` around lines 42 - 44, Update the MongoDB first-boot service journal instructions around the journalctl command to tell users to press Ctrl-C after the READY entry, or replace the live follow with a finite status/log command that exits automatically.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Outside diff comments:
In `@src/content/docs/public-cloud/marketplace/mongodb.md`:
- Around line 42-44: Update the MongoDB first-boot service journal instructions
around the journalctl command to tell users to press Ctrl-C after the READY
entry, or replace the live follow with a finite status/log command that exits
automatically.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 920aa4bf-0a9c-447a-9ed4-d20c670f5653
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (29)
package.jsonsrc/content/docs/fr/public-cloud/marketplace/erpnext.mdsrc/content/docs/fr/public-cloud/marketplace/gatus.mdsrc/content/docs/fr/public-cloud/marketplace/gitea.mdsrc/content/docs/fr/public-cloud/marketplace/haproxy.mdsrc/content/docs/fr/public-cloud/marketplace/harbor.mdsrc/content/docs/fr/public-cloud/marketplace/mattermost.mdsrc/content/docs/fr/public-cloud/marketplace/medusa.mdsrc/content/docs/fr/public-cloud/marketplace/mongodb.mdsrc/content/docs/fr/public-cloud/marketplace/neo4j.mdsrc/content/docs/fr/public-cloud/marketplace/nexus.mdsrc/content/docs/fr/public-cloud/marketplace/pterodactyl.mdsrc/content/docs/fr/public-cloud/marketplace/rabbitmq.mdsrc/content/docs/fr/public-cloud/marketplace/uptime-kuma.mdsrc/content/docs/fr/public-cloud/storage/object-storage/s3-usage.mdxsrc/content/docs/public-cloud/marketplace/erpnext.mdsrc/content/docs/public-cloud/marketplace/gatus.mdsrc/content/docs/public-cloud/marketplace/gitea.mdsrc/content/docs/public-cloud/marketplace/haproxy.mdsrc/content/docs/public-cloud/marketplace/harbor.mdsrc/content/docs/public-cloud/marketplace/mattermost.mdsrc/content/docs/public-cloud/marketplace/medusa.mdsrc/content/docs/public-cloud/marketplace/mongodb.mdsrc/content/docs/public-cloud/marketplace/neo4j.mdsrc/content/docs/public-cloud/marketplace/nexus.mdsrc/content/docs/public-cloud/marketplace/pterodactyl.mdsrc/content/docs/public-cloud/marketplace/rabbitmq.mdsrc/content/docs/public-cloud/marketplace/uptime-kuma.mdsrc/content/docs/public-cloud/storage/object-storage/s3-usage.mdx
🚧 Files skipped from review as they are similar to previous changes (22)
- src/content/docs/fr/public-cloud/storage/object-storage/s3-usage.mdx
- src/content/docs/public-cloud/marketplace/uptime-kuma.md
- src/content/docs/public-cloud/marketplace/gitea.md
- src/content/docs/public-cloud/marketplace/erpnext.md
- src/content/docs/public-cloud/marketplace/medusa.md
- src/content/docs/public-cloud/marketplace/pterodactyl.md
- src/content/docs/fr/public-cloud/marketplace/haproxy.md
- src/content/docs/public-cloud/storage/object-storage/s3-usage.mdx
- src/content/docs/public-cloud/marketplace/gatus.md
- src/content/docs/public-cloud/marketplace/nexus.md
- src/content/docs/fr/public-cloud/marketplace/gatus.md
- src/content/docs/fr/public-cloud/marketplace/harbor.md
- src/content/docs/public-cloud/marketplace/neo4j.md
- src/content/docs/public-cloud/marketplace/mattermost.md
- src/content/docs/public-cloud/marketplace/haproxy.md
- src/content/docs/public-cloud/marketplace/harbor.md
- src/content/docs/fr/public-cloud/marketplace/rabbitmq.md
- src/content/docs/fr/public-cloud/marketplace/erpnext.md
- src/content/docs/fr/public-cloud/marketplace/medusa.md
- src/content/docs/fr/public-cloud/marketplace/mattermost.md
- src/content/docs/fr/public-cloud/marketplace/neo4j.md
- src/content/docs/fr/public-cloud/marketplace/nexus.md
What changed
Why
Summary by CodeRabbit
Bug Fixes
portforward listcolumn mapping fixed.ssh-key deletenow supports key ID/name/slug; deleting unknown keys is a no-op.Documentation
s3cmdusage docs and expanded Marketplace guides/landing content across multiple services.Security
Chores