i-doit configuration should prioritize consistent object modeling, role-based access, and reliable import/sync workflows.
- database connection and PHP runtime limits
- category/object templates
- rights and role groups
- discovery/sync connectors
Example baseline values:
IDOIT_URL=https://idoit.example.com
DB_HOST=127.0.0.1
DB_NAME=idoit
DB_USER=idoit
DB_PASSWORD=replace-with-strong-password
- Define naming conventions for systems, services, and locations.
- Enforce status lifecycle (planned, productive, retired).
- Use templates for recurring object classes.
- Prevent free-form category sprawl by governance review.
¶ Integration and import policy
- Control discovery import scope before production sync.
- Use scheduled imports with change/audit logs.
- Map external system IDs to stable CI identifiers.
¶ Backup and recovery
Back up:
- MySQL/MariaDB database
- uploaded files/attachments
- custom report and template definitions
Recovery test:
- Restore DB and files.
- Validate object search and relationship graphs.
- Run one integration import in dry-run mode.
- DB growth and query latency monitored.
- Role assignments reviewed regularly.
- Import jobs monitored for drift/failure.
- Upgrade rollback plan documented.
Every deployment is unique. We provide consulting for:
- 🎯 Performance tuning for your workload
- 🔒 Security hardening and compliance (PCI-DSS, HIPAA, SOC2)
- 📊 Monitoring integration (Prometheus, Grafana, ELK)
- 🔄 High-availability and disaster recovery
Get personalized assistance: office@linux-server-admin.com | Contact Page