vladimirzobachov/mycrm

Purpose and Entry Points

This is a server-rendered PHP application centered on user accounts and order workflows, inferred from order, user, login, registration, and notification templates. The HTTP entry point is index.php; Apache routing/access behavior may be controlled by .htaccess. The supplied README is empty.

Request and Presentation Layer

index.php likely coordinates request dispatch, authentication/session behavior, form handling, database access, and template rendering. HTML views are file-based rather than a frontend application:

• templates/index.html

• templates/mai_create_order_owner.html

• templates/users.html

Static browser assets are served from:

• media/base.js

• media/style.css

• media/jquery-ui.js

Order and User Workflow Domain

The principal domain boundary is an order-management process with distinct owner, administrator, and mounter-oriented communications. Templates indicate create, edit, status-change, and comment-change events, with separate recipient variants:

• templates/mai_create_order_owner.html

• templates/mail_change_status_for_admin.html

• templates/mail_bind_mounter.html

User lifecycle screens are represented by templates/login.html, templates/register.html, and templates/user.html.

Form Input and Configuration

Form definitions or field mappings are centralized separately from rendering, suggesting a configurable request-validation/data-binding boundary:

• includes/form.class.php

• configs/form_data.php

This layer should translate HTTP form data into domain/database operations and select resulting templates or notification actions.

Persistence Boundary

Database access is abstracted behind a concrete class and interface, with connection settings isolated from consumers:

• includes/db_interface.class.php

• includes/db.class.php

• includes/dbconfig.php

No database engine or schema is present in the tree. Treat the interface as the primary seam for persistence changes and avoid coupling request/template code directly to connection details.

Notification Delivery

Email notifications are a first-class side effect of order changes. Application mail orchestration and templates are separated from the vendored PHPMailer transport implementation:

• includes/phpmailer/mailer.php

• includes/phpmailer/PHPMailer.php

• templates/mail_create_order_for_admin.html

The external-service boundary is SMTP/email delivery; host credentials and transport choices are not visible in the supplied files.

Spreadsheet Export Capability and Runtime

The repository vendors PHPExcel, providing workbook creation, calculation, import/export, and format writers. It is likely available for reporting or data export, although no application-level caller is visible:

• includes/PHPExcel/Classes/PHPExcel.php

• includes/PHPExcel/Classes/PHPExcel/IOFactory.php

• includes/PHPExcel/Classes/PHPExcel/Writer/Excel2007.php

The runtime is PHP deployed behind Apache. PHPExcel may rely on PHP extensions or optional cache backends, but their deployment configuration is not represented here.