How anshitsharma/ims-ftp works
This is a PHP infrastructure-management backend for cataloguing components, configuring servers, managing rack/location inventory, and running ticket-based operational pipelines. The main workflow enters through the API, uses domain handlers and pipeline orchestration to validate and apply configuration or workflow actions, then reports resulting state. The graph emphasizes the documented pipeline engine, component-specification and compatibility/validation layers, and location/rack capabilities. The README is empty and many handlers are unsampled, so only indexed or excerpt-supported relationships are shown.
Main entry points: PipelineManager.php Pipeline engine · api.php API router · LocationResolver.php Location resolver · ComponentDataService.php Component data
Components 27
API and identity
- API router
api/api.php - Authentication handlers
api/handlers/auth - ACL handlers
api/handlers/acl - Microsoft OAuth
core/auth/MicrosoftOAuth.php
Pipeline workflows
- Pipeline handlers
api/handlers/pipelines - Pipeline engine
core/models/pipelines/PipelineManager.php - Pipeline templates
core/models/pipelines/PipelineTemplateManager.php - Action executor
core/models/pipelines/RequestActionExecutor.php - Ticket services
core/models/tickets - Workflow config
core/config/WorkflowConfig.php
Inventory and location
- Server handlers
api/handlers/server/server_api.php - Rack handlers
api/handlers/rack/rack_api.php - Location handlers
api/handlers/location/location_api.php - Location resolver
core/models/location/LocationResolver.php - Inventory services
core/helpers/Inventory.php
Configuration and validation
- Server builder
core/models/server/ServerBuilder.php - Component data
core/models/components/ComponentDataService.php - Spec paths
core/models/components/ComponentSpecPaths.php - Compatibility checks
core/models/compatibility/StorageConnectionValidator.php - Validation engine
core/models/validation/ValidationEngine.php - Validation rules
core/models/validation/rules - Target state
core/models/validation/TargetState.php
Shared services
- Request parsing
core/helpers/RequestHelper.php - Schema probes
core/helpers/SchemaHelper.php - Notifications
core/helpers/NotificationService.php
Other components
- API client
- Application database
Connections 35
- API client → API router: sends requests
- API router → Authentication handlers: routes to
api/api.php - API router → Server handlers: routes to
api/api.php - API router → Rack handlers: routes to
api/api.php - API router → Location handlers: routes to
api/api.php - API router → ACL handlers: routes to
api/api.php - API router → Request parsing: loads
api/api.php - Pipeline handlers → Request parsing: parses requests
api/handlers/pipelines/pipeline-create.php - Pipeline handlers → Pipeline engine: creates pipelines
api/handlers/pipelines/pipeline-create.php - Pipeline engine → Pipeline templates: uses templates
core/models/pipelines/PipelineManager.php - Pipeline engine → Ticket services: uses ticket services
core/models/pipelines/PipelineManager.php - Pipeline engine → Action executor: executes actions
core/models/pipelines/PipelineManager.php - Pipeline engine → Workflow config: reads config
core/models/pipelines/PipelineManager.php - Pipeline engine → Server builder: builds servers
core/models/pipelines/PipelineManager.php - Pipeline engine → Location resolver: resolves locations
core/models/pipelines/PipelineManager.php - Pipeline engine → Notifications: loads notifications
core/models/pipelines/PipelineManager.php - Pipeline engine → Application database: updates records
core/models/pipelines/PipelineManager.php - Pipeline engine → API client: returns outcome
core/models/pipelines/PipelineManager.php - Server handlers → Application database: reads and writes
- Rack handlers → Application database: reads and writes
- Location handlers → Location resolver: resolves locations
- Location resolver → Schema probes: probes schema
core/models/location/LocationResolver.php - Location resolver → Application database: queries location data
core/models/location/LocationResolver.php - Inventory services → Component data: uses component data
core/helpers/Inventory.php - Inventory services → Spec paths: reads spec paths
core/helpers/Inventory.php - Inventory services → Application database: accesses inventory
- Component data → Spec paths: resolves spec files
core/models/components/ComponentDataService.php - Compatibility checks → Component data: loads component data
core/models/compatibility/StorageConnectionValidator.php - Compatibility checks → Application database: checks configuration
- Validation engine → Validation rules: dispatches rules
core/models/validation/ValidationEngine.php - Validation rules → Target state: evaluates state
core/models/validation/rules/StorageBayCapacityRule.php - Validation engine → Target state: evaluates
core/models/validation/ValidationEngine.php - Server builder → Validation engine: validates configuration
core/models/server/ServerBuilder.php - Server builder → Component data: uses component specs
core/models/server/ServerBuilder.php - Microsoft OAuth → API client: authenticates