1 Commits

Author	SHA1	Message	Date
yekk	77ae7b5dd9	Feature/mytess restructure (#6) ... * Restructure repository for Mytess SEO optimization ## Changes ### File Reorganization - Move docker-compose files and images to new `script/` directory - Create new English root README.md with Mytess showcase - Add simplified Chinese README.zh.md as redirect - Add comprehensive English deployment guide in script/README.md ### Docker Compose Updates - Remove Chinese mirror sources (docker.1ms.run) from all images - Use official Docker registry for global compatibility - Add cache headers for Dash static assets (1-year cache) - Configure caching for Next.js static files and PWA assets ### SEO & Documentation - Feature Mytess prominently with screenshots and links - Include App Store and mytess.net references - Natural keyword integration for TeslaMate iOS/mobile searches - Comprehensive troubleshooting and configuration guides - Architecture diagrams for both deployment options ### Benefits - Improved global search visibility for Mytess - Better user experience with clear English documentation - Performance improvements via static asset caching - Maintained backward compatibility for existing users Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> * Remove emojis and add showcase images to README ## Changes - Remove all emoji icons from both English and Chinese READMEs - Add actual showcase images from mytess-web project - Update feature descriptions with paired screenshots - Include images for: drive insights, cost management, map mode, and notifications - Maintain professional and clean documentation style Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> * Switch to official TeslaMate images and clarify version differences ## Changes ### Docker Compose Updates - **Basic version (docker-compose.yml)**: Now uses official images - teslamate/teslamate:latest (was mytesla/teslamate:v2.2) - teslamate/grafana:latest (was mytesla/grafana:v2.2) - **Mytesla version (docker-compose-with-mytesla.yml)**: Unchanged, continues using mytesla images ### Documentation Updates - **English README**: Clarify two deployment options with clear use cases - Option 1: Official version for international users - Option 2: Mytesla optimized for China (with problem solutions listed) - **Chinese README**: Add detailed explanation of mytesla version benefits - OpenStreetMap proxy solution - Baidu Maps support - Chinese localization - Unified authentication - **script/README.md**: Update deployment instructions with version comparison ### Benefits - Users can now choose between official and optimized versions - Clear guidance on which version to use based on location - Mytesla version value proposition clearly explained (China-specific fixes) - Maintains flexibility for different user needs Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> * Add Mytesla Dash licensing information ## Changes - Add FAQ entry about Mytesla Dash license requirement - Direct users to contact hi@mytesla.cc for licensing inquiries - Add note in script/README.md for Mytesla Dash option - Replace Chinese-specific licensing link with international email contact Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> * Use official TeslaMate/Grafana images in both configurations ## Changes ### Docker Compose Updates Both versions now use official TeslaMate and Grafana images: - `teslamate/teslamate:v2.2` (official) - `teslamate/grafana:v2.2` (official) **Basic version (docker-compose.yml)**: - Official TeslaMate + Grafana only **Mytesla version (docker-compose-with-mytesla.yml)**: - Official TeslaMate + Grafana as base - Plus Mytesla enhancement components: - mytesla/auth - Unified authentication - mytesla/dash - Modern web dashboard - mytesla/teslamateapi - Enhanced API - mytesla/env-adapter - Environment adapter ### Documentation Updates - Update all READMEs to reflect official image usage - Clarify that Mytesla version = Official base + Mytesla components - Explain advantages of Mytesla components in Chinese docs - Remove "China-specific" positioning, focus on feature benefits ### Benefits - Both versions stay up-to-date with official TeslaMate releases - Mytesla version provides additional value through enhancement components - Clear separation: official base vs. enhanced features - Users can choose based on feature needs, not geography Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> * Add TeslaMateAPI to basic docker-compose configuration ## Changes ### Docker Compose - Add official TeslaMateAPI service to basic version - Image: tobiasehlert/teslamateapi:latest - Port: 8080 (standard TeslaMateAPI port) - Enable API commands and token authentication - Configure database and MQTT connections ### Documentation Updates - Update all port references from 3030 to 8080 - Add TeslaMateAPI to basic version service list - Update firewall instructions to include port 8080 - Clarify that basic version now supports Mytess iOS app ### Benefits - Basic version now fully supports Mytess iOS app connectivity - Users can choose between: - Basic: Separate ports (4000, 3000, 8080) - Mytesla: Unified port 80 with reverse proxy - No need to use Mytesla version just for API access Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> * Fix basic version TeslaMateAPI configuration ## Changes ### Docker Compose - Change image to mytesla/teslamateapi:latest (match with-mytesla version) - Update port mapping to 3030:8080 (consistent with documentation) - Align environment variables with with-mytesla version: - Add API_TOKEN configuration - Add teslamateapi-data volume - Add teslamate dependency - Remove unnecessary logging configuration ### Documentation - Update all API port references back to 3030 - Ensure consistency across all README files ### Result - Basic version now uses same API image as Mytesla version - Configuration is consistent and simpler - Port 3030 is standard for TeslaMateAPI external access Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> * Fix TeslaMateAPI authentication description ## Changes - Correct API access description from "(no auth required)" to "(requires API token)" - TeslaMateAPI does require API_TOKEN for authentication - Although it bypasses Traefik ForwardAuth, it still needs token validation Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> * Remove China-specific language and TeslaMateAPI reference from English docs ## Changes ### README.md - Remove "optimized for mainland China" from subtitle - Replace "China-Specific Optimizations" with generic feature benefits - Remove China-related notes about map loading issues - Remove TeslaMateAPI GitHub link from Related Projects - Focus on universal features: Mytess integration, modern interface ### script/README.md - Change "recommended for China" to "recommended" (universal) - Remove China-specific troubleshooting (Baidu Maps references) - Use generic network troubleshooting guidance ### Rationale - Make English documentation internationally focused - Chinese-specific information remains in README.zh.md - Avoid geographic positioning in global documentation - Remove redundant API reference (already integrated in project) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> * Update repository URLs to new location ## Changes - Update all git clone URLs from old repository to new location - Old: github.com/gococonut/teslamate-cn-image - New: github.com/yekk-me/teslamate-mytess-docker - Update directory names in cd commands to match new repo name - Update GitHub Issues links ### Files Updated - README.md (English) - README.zh.md (Chinese) - script/README.md Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> * Recommend mytesla images for Chinese users and explain benefits ## Changes in README.zh.md ### Image Recommendations - Change to recommend mytesla/teslamate:v2.2 for Chinese users - Change to recommend mytesla/grafana:v2.2 for Chinese users - Keep official images as "Option 1" for international users ### Added "Mytesla 镜像解决的问题" Section Clearly explain China-specific problems solved by mytesla images: - ✓ OpenStreetMap proxy for map loading in mainland China - ✓ Baidu Maps geocoding integration for accurate locations - ✓ Complete Chinese localization and pre-configured dashboards - ✓ Network optimizations for China ### Positioning - Chinese README now recommends mytesla images (China-optimized) - English README uses official images (international) - Clear value proposition for Chinese users Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> * Fix PostgreSQL data directory mount path ## Changes - Fix database volume mount in docker-compose-with-mytesla.yml - Change from `/var/lib/postgresql` to `/var/lib/postgresql/data` - PostgreSQL official image stores data in `/var/lib/postgresql/data` - Now consistent with basic version configuration ### Impact - Ensures data is properly persisted in the correct directory - Prevents potential data loss issues - Matches PostgreSQL best practices Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> * Fix PostgreSQL mount and add Baidu Maps configuration guide ## Changes ### PostgreSQL Volume Mount Fix - Remove `/data` from PostgreSQL mount paths in both files - Correct path: `/var/lib/postgresql` (not `/var/lib/postgresql/data`) - Applies to both docker-compose.yml and docker-compose-with-mytesla.yml ### Chinese README Enhancement Add Baidu Maps configuration section for accurate geocoding: - Instructions to obtain BD_MAP_AK and BD_MAP_SK - Step-by-step guide for Chinese users - Explains benefit: accurate Chinese location names vs English addresses - Example configuration in teslamate service environment ### Rationale - PostgreSQL 18 uses `/var/lib/postgresql` as data directory - Baidu Maps improves location accuracy for Chinese users - Solves reverse geocoding issues in mainland China Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>	2026-02-07 10:25:33 +08:00