docs: add HTTPS production deployment guide with nginx reverse proxy#402
Merged
its-me-abhishek merged 1 commit intomainfrom Jan 19, 2026
Merged
docs: add HTTPS production deployment guide with nginx reverse proxy#402its-me-abhishek merged 1 commit intomainfrom
its-me-abhishek merged 1 commit intomainfrom
Conversation
Add configuration examples and documentation for deploying CCSync with HTTPS using nginx as a reverse proxy with Let's Encrypt SSL certificates. New files: - production/example.frontend.env: Example frontend environment variables - production/example.nginx.conf: nginx reverse proxy configuration with SSL termination for the main site (port 443) and sync server (port 8080) Updated: - production/README.md: Reorganized into three deployment options: 1. Docker (HTTP only, for local/dev) 2. Docker with nginx reverse proxy (HTTPS, recommended for production) 3. Kubernetes The nginx config includes: - HTTP to HTTPS redirect - SSL configuration with modern cipher suites - Proxy rules for all backend API routes - WebSocket support for /ws endpoint - SSL termination for taskchampion sync server on port 8080 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
|
Thank you for opening this PR! Before a maintainer takes a look, it would be really helpful if you could walk through your changes using GitHub's review tools. Please take a moment to:
More information on how to conduct a self review: This helps make the review process smoother and gives us a clearer understanding of your thought process. Once you've added your self-review, we'll continue from our side. Thank you! |
its-me-abhishek
approved these changes
Jan 19, 2026
its-me-abhishek
approved these changes
Jan 19, 2026
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
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.
Summary
example.frontend.env)example.nginx.conf)Changes
New Files
production/example.frontend.env: Example frontend environment variables for HTTPS deploymentproduction/example.nginx.conf: Complete nginx configuration with:/auth/,/api/,/tasks, etc.)/wsendpointUpdated Files
production/README.md: Reorganized into three deployment options:Why
Google OAuth requires HTTPS redirect URIs for production deployments (HTTP is only allowed for localhost). This guide provides a complete, tested configuration for deploying CCSync with proper SSL support.
Test plan
🤖 Generated with Claude Code