How tblacerda/conexaovida works
Project type and purpose
• From the file tree and README we see two major parts:
• “APP” – a Cordova/Ionic hybrid mobile front-end built with AngularJS, SCSS, Gulp and Bower.
• “WS-master” – a PHP-Slim based RESTful back-end (controllers, DAO layer, PHPMailer utility), with a MySQL schema.
• Purpose: A mobile app (“ConexaoVida”) for users to register symptoms, exams, notifications, patients, appointments, chat-bot interactions, backed by a web service.
File structure
• APP folder:
– config.json, gulpfile.js, package.json – build & config.
– www/ – compiled assets: index.html, templates (HTML views), js/ (Angular controllers, constants, util), lib/ (Ionic, Angular, Angular-UI-Router, Ionic-Material, waves, dataTables), css/, img/, service-worker.
– hooks/ – Cordova lifecycle scripts.
• WS-master folder:
– index.php, Slim framework (in /Slim and /midle/iconfigmidlews), application controllers (/control), DAOs (/dao), models (/model), configuration (config.php, config.ini), utilities (/util), PHPMailer under util/mailer.
– Banco-imip .mwb – MySQL Workbench files.
README
• This is a placeholder Readme with no architecture details. The project name at bottom (“ConexaoVida”) hints at medical/health context. We infer from code locations: controllers → DAO → DB.