docs/self-hosted/bitbucket.md (4)

8-12:Improve note formatting for better visibility

Consider using a more prominent callout style for this important enterprise requirement.

-:::note+:::important

---

37-37:Replace localhost example with a production-like URL

The example URL uses localhost which might be misleading for production setups. Consider using a more realistic example.

-3. **Add Webhook URL**: Enter the URL pointing to the CodeRabbit service, followed by `/bitbucket_server_webhooks` (e.g., `http://127.0.0.1:8080/bitbucket_server_webhooks`).+3. **Add Webhook URL**: Enter the URL pointing to the CodeRabbit service, followed by `/bitbucket_server_webhooks` (e.g., `https://coderabbit.your-domain.com/bitbucket_server_webhooks`).

---

113-113:Add production security note for Docker exposure

The current Docker command binds to localhost, which won't work in production. However, exposing the service needs careful consideration.

-docker run --env-file .env --publish 127.0.0.1:8080:8080 us-docker.pkg.dev/coderabbitprod/self-hosted/coderabbit-agent:latest+# For development/testing+docker run --env-file .env --publish 127.0.0.1:8080:8080 us-docker.pkg.dev/coderabbitprod/self-hosted/coderabbit-agent:latest++# For production (ensure proper security measures are in place)+docker run --env-file .env --publish 8080:8080 us-docker.pkg.dev/coderabbitprod/self-hosted/coderabbit-agent:latest

Consider adding a security note:

:::cautionWhen deploying to production, ensure proper security measures (e.g., reverse proxy, SSL/TLS, firewall rules) are in place before exposing the service to external traffic.:::

---

114-114:Add a troubleshooting section

Consider adding a "Troubleshooting" section at the end of the document to help users diagnose and resolve common issues they might encounter during setup and operation.

Example topics to cover:

• Common webhook configuration issues
• Authentication problems
• Docker container startup issues
• Health check failures

Would you like me to help draft a troubleshooting section?

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

#!/bin/bash# Check other documentation files' sidebar positionsfd -e md. docs/self-hosted/ -x grep -l"sidebar_position" {}\;| xargs awk'/sidebar_position:/ {printf "%s: %s\n", FILENAME, $0}'

docs/self-hosted/bitbucket.md (2)

23-24:Consider adding specific permission levels

The current permissions list is quite high-level. Consider adding more specific details about the required permission levels (e.g., "Read" vs "Write" access) and any specific project roles that should be assigned.

---

110-110:Add HTTPS requirements for production deployments

The documentation should emphasize the importance of configuring HTTPS for production deployments. Consider adding a section about:

• SSL/TLS certificate requirements
• Reverse proxy configuration examples (e.g., nginx)
• Security best practices for exposing the service

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

#!/bin/bash# Search for any other instances of sales email to ensure consistencyrg -i"sales@.*\.ai"

docs/self-hosted/bitbucket.md (2)

2-2:Fix double spaces in title and description

Remove the extra spaces in these lines:

-title: Use Self-Hosted CodeRabbit With  Bitbucket Datacenter+title: Use Self-Hosted CodeRabbit With Bitbucket Datacenter-description: Instructions to self-host CodeRabbit and integrate it with  Bitbucket Datacenter.+description: Instructions to self-host CodeRabbit and integrate it with Bitbucket Datacenter.

Also applies to: 4-4

---

57-57:Fix typo in Azure deployment name variable

There's a typo in the Azure deployment name variable:

-AZURE_GPT4OMINI_DEPLOYMENT_NAME=<gpt-4o-mini-deployment-name>+AZURE_GPT4O_MINI_DEPLOYMENT_NAME=<gpt-4o-mini-deployment-name>

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro