Initial commit: ROA2WEB - FastAPI + Vue.js + Telegram Bot
Modern ERP Reports Application with microservices architecture Tech Stack: - Backend: FastAPI + python-oracledb (Oracle DB integration) - Frontend: Vue.js 3 + PrimeVue + Vite - Telegram Bot: python-telegram-bot + SQLite - Infrastructure: Shared database pool, JWT authentication, SSH tunnel Features: - FastAPI backend with async Oracle connection pool - Vue.js 3 responsive frontend with PrimeVue components - Telegram bot alternative interface - Microservices architecture with shared components - Complete deployment support (Linux Docker + Windows IIS) - Comprehensive testing (Playwright E2E + pytest) Repository Structure: - reports-app/ - Main application (backend, frontend, telegram-bot) - shared/ - Shared components (database pool, auth, utils) - deployment/ - Deployment scripts (Linux & Windows) - docs/ - Project documentation - security/ - Security scanning and git hooks
This commit is contained in:
34
ssh-tunnel/README_SSH_KEY.md
Normal file
34
ssh-tunnel/README_SSH_KEY.md
Normal file
@@ -0,0 +1,34 @@
|
||||
# SSH Key Configuration
|
||||
|
||||
## 🔐 SSH Private Key Location
|
||||
|
||||
The SSH private key `roa_oracle_server` has been moved to a secure location for security reasons.
|
||||
|
||||
### Current Location:
|
||||
```
|
||||
roa2web/secrets/roa_oracle_server
|
||||
```
|
||||
|
||||
### Security Measures Applied:
|
||||
- ✅ File moved to `secrets/` directory (protected by .gitignore)
|
||||
- ✅ File permissions set to 600 (owner read/write only)
|
||||
- ✅ Directory `secrets/` is excluded from git tracking
|
||||
|
||||
### Usage in Scripts:
|
||||
Update any scripts that reference the SSH key to use the new path:
|
||||
|
||||
```bash
|
||||
# Old path (INSECURE):
|
||||
# ssh -i roa2web/ssh-tunnel/roa_oracle_server
|
||||
|
||||
# New path (SECURE):
|
||||
ssh -i roa2web/secrets/roa_oracle_server
|
||||
```
|
||||
|
||||
### Important Notes:
|
||||
- ⚠️ The SSH key is no longer tracked in git history after security cleanup
|
||||
- 🔄 Consider regenerating the SSH key if it was compromised
|
||||
- 📋 Ensure all team members update their scripts to use the new path
|
||||
|
||||
---
|
||||
*SSH key secured: 2025-08-03*
|
||||
Reference in New Issue
Block a user