a604a3cc44
- Implemented test scripts for vTiger account retrieval, contact data, and modules. - Created a detailed test suite for the ticket module, covering database schema validation, ticket number generation, prepaid card constraints, and service logic. - Added tests for vTiger field inspection and various queries related to accounts and sales orders. - Introduced SQL migration scripts for the ALSO Cloud Billing foundation, including import jobs, lines, and mapping tables with necessary constraints and indices. - Enhanced workflow columns in the import lines table to support matching and validation timestamps.
26 lines
1.1 KiB
Markdown
26 lines
1.1 KiB
Markdown
# BMC Hub v2.1.1 - Bug Fix Release
|
|
|
|
**Release Date:** 29. januar 2026
|
|
|
|
## 🐛 Bug Fixes
|
|
|
|
### Migrationer Interface
|
|
- **Fixed container runtime detection**: Production servers using Podman now show correct commands instead of Docker commands
|
|
- **Updated migration command display**: Frontend now correctly shows `podman exec` commands for production environments
|
|
- **Improved user experience**: Added container runtime information in the standard setup section
|
|
|
|
## 🔧 Technical Changes
|
|
|
|
- Updated `app/settings/frontend/migrations.html` to detect production environment and use appropriate container runtime
|
|
- Modified `app/settings/backend/views.py` to pass production environment flag to template
|
|
- Container runtime detection based on hostname (production vs localhost/127.0.0.1)
|
|
|
|
## 📋 Deployment Notes
|
|
|
|
This is a frontend-only change that fixes the migration interface display. No database changes required.
|
|
|
|
## ✅ Verification
|
|
|
|
- Migration page now shows correct Podman commands on production servers
|
|
- Local development still uses Docker commands
|
|
- Migration execution via web interface continues to work as before |