Commit Graph

18 Commits

Author SHA1 Message Date
8d9c216c88 Fix: Correct Tor routing configuration - Enable Privacy__EnableTor
## Issue
Previous fix enabled LittleShop__UseTor=true, which tried to route internal
Docker API calls through Tor. Tor correctly rejected these private addresses.

## Root Cause
Two separate Tor configuration flags exist:
1. Privacy__EnableTor - Controls Telegram Bot API calls (external, public)
2. LittleShop__UseTor - Controls LittleShop API calls (internal, private)

## Solution
- Set LittleShop__UseTor=false (internal calls direct - no Tor)
- Set Privacy__EnableTor=true (Telegram API calls via Tor)

## Impact
 Telegram Bot API calls now route through Tor (privacy protected)
 Internal API calls go direct (no Tor rejection errors)
 Proper separation of concerns

## Technical Details
TelegramBotService.cs:77 checks Privacy:EnableTor
Program.cs:63 checks LittleShop:UseTor
These control different HTTP clients for different purposes.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-03 17:53:04 +01:00
129e7edb75 Enable Tor routing for TeleBot - Privacy Enhancement
## Issue
TeleBot was bypassing Tor gateway despite infrastructure being available.

## Root Cause
Deployment configuration explicitly disabled Tor:
- LittleShop__UseTor=false (line 118)

## Fix
Changed deployment configuration to enable Tor routing:
- LittleShop__UseTor=true

## Impact
 All Telegram API calls now route through Tor network
 Bot's real IP hidden from Telegram servers
 Enhanced privacy protection
⚠️ Slight latency increase due to Tor overhead

## Verification Required
Monitor tor-gateway logs after deployment to confirm traffic routing.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-03 17:44:13 +01:00
sysadmin
3a8d576b64 "Preserve-TeleBot-configuration-in-CI-CD" 2025-10-03 16:43:32 +01:00
sysadmin
21588230d7 "Fix-TeleBot-TOR-proxy-configuration" 2025-10-03 16:07:01 +01:00
sysadmin
e0c431cbae "CI-CD-Add-TeleBot-build-and-deployment" 2025-10-03 16:00:05 +01:00
c31df615ab Revert .gitlab-ci.yml to working configuration
Keep authentication fix in Program.cs but use original CI/CD pipeline configuration that builds from Dockerfile

🤖 Generated with Claude Code

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-01 13:18:19 +01:00
d31c0b4aeb CI/CD: Add GitLab CI/CD pipeline for Hostinger deployment
- Updated .gitlab-ci.yml with complete build, test, and deploy stages
- Added authentication redirect fix in Program.cs (302 redirect for admin routes)
- Fixed Cookie vs Bearer authentication conflict for admin panel
- Configure pipeline to build from .NET 9.0 source
- Deploy to Hostinger VPS with proper environment variables
- Include rollback capability for production deployments

🤖 Generated with Claude Code

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-01 13:10:48 +01:00
51cc0463de Update .gitlab-ci.yml file 2025-09-29 18:12:34 +02:00
37687757bb Revert "Update .gitlab-ci.yml file" 2025-09-29 18:07:37 +02:00
fb3269e680 Update .gitlab-ci.yml file 2025-09-29 17:58:58 +02:00
84b0a880f6 Update .gitlab-ci.yml file 2025-09-29 17:44:10 +02:00
8a7c07ead7 Fix CI/CD: Add Docker network cleanup to prevent pool conflicts 2025-09-28 19:02:26 +01:00
7ffb3de3f2 Fix CI/CD: Force cleanup orphan containers before deployment 2025-09-28 19:00:09 +01:00
191a9f27f2 Enable auto-deploy for LittleShop on main branch
- Added auto-deploy on successful builds for main branch
- Deployment uses commit SHA when no tag is present
- Manual deployment still available for tagged releases
- Follows same pattern as TeleBot deployment

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-09-27 09:54:48 +01:00
e75411dab9 Fix health check port to 5100 (host port) 2025-09-27 08:03:06 +01:00
d57f3ddd59 Fix SSH variable quoting in GitLab CI/CD 2025-09-27 07:47:57 +01:00
849d4994de Fix GitLab CI/CD Docker socket configuration
Remove docker:24-dind service to use runner's mounted Docker socket.
This fixes the 403 Git access error and Docker socket conflict.

Changes:
- Remove services: docker:24-dind from build and deploy jobs
- Change image from docker:24-dind to docker:24
- Update DOCKER_HOST to use unix socket

Co-Authored-By: Claude <noreply@anthropic.com>
2025-09-27 07:39:48 +01:00
6c05b7d0e8 Add GitLab CI/CD deployment pipeline
- Add .gitlab-ci.yml with build, deploy, and rollback stages
- Add docker-compose.production.yml (security-compliant, no hardcoded secrets)
- Update .env.example with SilverPay integration variables
- Add GITLAB-CI-DEPLOYMENT.md documentation

Security improvements:
- All secrets in VPS .env file (never in Git)
- Environment variables without defaults (fail-fast)
- SSH key authentication for CI/CD
- VPN-only access via hq.lan

Co-Authored-By: Claude <noreply@anthropic.com>
2025-09-27 07:05:02 +01:00