✨ Новые скрипты:
- scripts/check-nginx.sh - полная диагностика nginx
- scripts/nginx-quick-check.sh - быстрая проверка
🔧 Новые команды Makefile:
- make check-nginx - быстрая проверка
- make check-nginx-full - полная диагностика
📊 Что проверяют скрипты:
- Статус службы nginx
- Корректность конфигурации
- Прослушиваемые порты (80, 443)
- Доступность backend/frontend сервисов
- Проксирование через nginx
- Доменные имена и DNS
- SSL сертификаты
- Анализ логов и конфигурации
- Рекомендации по исправлению
📝 Документация:
- docs/NGINX_DIAGNOSTICS.md - руководство по диагностике
🎯 Использование на сервере:
- ./scripts/nginx-quick-check.sh
- ./scripts/check-nginx.sh
- Создан docker-compose.prod.yml для продакшен конфигурации
- Добавлена команда up-prod в Makefile для запуска в продакшен режиме
- Обновлен .env файл с правильными настройками для продакшена
- Исправлены проблемы с паролем PostgreSQL
- Система полностью развернута и работает
- Fix bash error in generate_env.sh with proper environment variable handling
- Add docker-compose command detection for better compatibility
- Add generate-env-prod command with production warnings
- Make generate-env non-interactive by default for easier automation
- Add generate-env-interactive for when user input is needed
- Expand .env.example with more configuration options
- Add helpful production deployment warnings
Resolves: 'make generate-env generates nonsense' issue
- Replace prose-lg with prose-text using standard text-lg utility
- Remove duplicate typography layer definitions
- Clean up CSS structure to use only core Tailwind utilities
- Resolve 'Cannot apply unknown utility class prose-lg' error
Frontend Docker build now succeeds with only minor @screen warnings
- Remove reference to non-existent test-styles.css file in globals.css
- This resolves frontend build error in Docker/CI environment
- Keep existing layouts.css import which exists and is valid
Fixes: Can't resolve './test-styles.css' webpack error
- Document resolution of 'bash: not found' error
- Add explanation of new sh-based script execution
- Update fallback logic documentation with latest improvements
- Provide clear migration path for users experiencing CI issues
This completes the Drone CI troubleshooting documentation
- Replace bash with sh for script execution to work with docker:dind image
- Add bash installation to prepare step for script compatibility
- Keep chmod +x for ensuring script permissions
- All scripts now use sh interpreter which is available by default
This resolves '/bin/sh: bash: not found' errors in Drone CI pipeline
- Replace ./scripts/ci/*.sh with bash scripts/ci/*.sh for better compatibility
- Add chmod +x before script execution to ensure permissions
- Add debugging info showing current directory and file permissions
- This should resolve the 'script not found' error even when files exist
The issue was that ./script.sh requires the script to be in PATH or current dir
with execute permissions, while bash script.sh explicitly invokes bash interpreter"
s
