C
Asked
Subject: Request for Technical Documentation and DB Schema Details
Dear Largua Support Team,
I hope you are doing well.
Following our technical review of the platform, we would like to request clarification on several points related to development and system architecture:
1- Licensing and Extensibility:
Can you confirm whether the platform license allows full source-code modification and custom feature development, or is it provided as a closed, production-ready product strictly for operational use?
2- Database Schema / Migrations:
We noticed that the database schema is not fully represented in the database/migrations directory.
- Are there additional migration files located elsewhere in the source tree?
- Or was the database generated manually without a full migration history?
3- System Architecture Documentation:
To support proper maintenance and further development, we kindly request:
- A complete architecture diagram illustrating the core modules, services, and data flow
- A database ERD (Entity-Relationship Diagram), or at least the full DB schema
- Any available technical documentation or onboarding guidelines for developers
Providing this information will greatly facilitate our ability to extend and customize the platform while maintaining alignment with your design standards.
Thank you for your support.
Kind regards,
Dear Largua Support Team,
I hope you are doing well.
Following our technical review of the platform, we would like to request clarification on several points related to development and system architecture:
1- Licensing and Extensibility:
Can you confirm whether the platform license allows full source-code modification and custom feature development, or is it provided as a closed, production-ready product strictly for operational use?
2- Database Schema / Migrations:
We noticed that the database schema is not fully represented in the database/migrations directory.
- Are there additional migration files located elsewhere in the source tree?
- Or was the database generated manually without a full migration history?
3- System Architecture Documentation:
To support proper maintenance and further development, we kindly request:
- A complete architecture diagram illustrating the core modules, services, and data flow
- A database ERD (Entity-Relationship Diagram), or at least the full DB schema
- Any available technical documentation or onboarding guidelines for developers
Providing this information will greatly facilitate our ability to extend and customize the platform while maintaining alignment with your design standards.
Thank you for your support.
Kind regards,
- MSAnsweredHello,
1. You can modify the sources code as you need under any license and use terms as per license. You can read the full license.
2. Yes, the installation will create the database and table. The migrations will only be available for update (if any).
- No.
- The database has migrations tables and will use that for future migrations.
3. You can check the guide at https://tecdiary.github.io/sma-guide/developer/
- It's standard Laravel application and has SMA related controllers in `app/Http/Controllers/Sma` while models in `app/Models/Sma` in the beta.6 all other Laravel folders are move to `app/Tec/`
- Once installed, you have the database and can draw diagrams using any software of your choice.
- Please refer to https://tecdiary.github.io/sma-guide/developer/
Thank you - Login to Reply