Loveria

Technical Guide

Technical Guide

Server Requirements

 

Server requirements as given below:

 

  • PHP >= 7.2.5
  • OpenSSL PHP Extension
  • PDO PHP Extension
  • Mbstring PHP Extension
  • Tokenizer PHP Extension
  • XML PHP Extension
  • Ctype PHP Extension
  • JSON PHP Extension
  • BCMath PHP Extension
  • Fileinfo PHP Extension
  • GD Library (>=2.0)
  • Curl
  • MySQL 5.7 +

 

Frameworks & Library Uses

 

To make this awesome product below are the libraries used:

 

PHP

  • Php - ^7.2.5
  • box/spout - ^3.1
  • fideloper/proxy - ^4.2
  • fruitcake/laravel-cors - ^1.0
  • firebase/php-jwt - ^5.0.0
  • fzaninotto/faker - ^1.9
  • gettext/gettext - ^5.2
  • gettext/php-scanner - ^1.1
  • guzzlehttp/guzzle - ^6.3
  • intervention/image - ^2.5.1
  • laravel/framework – 7.30.0
  • laravel/helpers - ~1.4.1
  • laravel/socialite - ^4.3.1
  • laravel/tinker - ^2.0
  • league/flysystem-aws-s3-v3 - ~1.0
  • mk-j/php_xlsxwriter - ^0.37.0
  • paypal/paypal-checkout-sdk - ^1.0.1
  • pusher/pusher-php-server - ~4.1.1
  • stripe/stripe-php - ^7.2.2
  • vemcogroup/laravel-sparkpost-driver - ^3.0.1
  • razorpay/razorpay - ^2.5.0
  • paypal/rest-api-sdk-php - ^1.14.0
     

JavaScript & CSS

 

  • @fortawesome/fontawesome-free - 5.12.1
  • agora-rtc-sdk - 3.3.0
  • animate.css - 3.7.2
  • bootstrap - 4.5.3
  • chart.js - 2.9.4
  • datatables.net - 1.10.22
  • datatables.net-bs4 - 1.10.22
  • datatables.net-responsive - 2.2.6
  • datatables.net-responsive-bs4 - 2.2.6
  • emojionearea - 3.4.2
  • filepond - 4.23.1
  • filepond-plugin-file-poster - 2.3.1
  • filepond-plugin-file-validate-type - 1.2.5
  • filepond-plugin-image-preview - 4.6.4
  • filepond-polyfill – 1.0.4
  • jquery - ^3.5.1
  • jquery-lazy - ^1.7.11
  • jquery-parallax.js - 1.5.0
  • jquery-validation - 1.19.2
  • jquery.easing - 1.4.1
  • lodash - 2.4.2
  • noty - 3.1.4
  • photoswipe - 4.1.3
  • pusher-js – 7.0.2
  • selectize - 0.12.6
  • smartwizard - 4.4.1
  • leaflet - 1.7.1

 

File Structure

While development we follow some of our rules to organize the code. For this we have made some changes to the Laravel framework files as follows:

 

Controllers

 

By default, Laravel placed all its controllers under Http/Controllers folder, our component controllers are placed App/Yantrana/Components/ in their respective component

 

File Structure

All the component code is placed under the folder called Yantrana under the app folder. This folder contains folders:

  • __Laraware – a files contain a core files for the various classes which mostly extends Laravel classes & helper, which are restricted to change while development.
  • Base – is also contains the base files for various classes which mostly extended using __Laraware classes.
  • Support – contains various & common helpers & classes.
  • Services – contains various & common required service classes.
  • Components – This is main folder which contains all the business logic in to its own modules as follows:
    • Component Folder

Each component has its own folder structure as follows:

  • Models – Contains all the model files.
  • Controllers – contains all the controller files.
  • Repositories – contains all the repositories which treated as data-layer.
  • Requests – contains the request files mostly for forms.
  • Blueprints – contains the interface files for required classes.
  • Engine.php – Its treated as most important file for the component

Each component can have multiple sub components.

 

public/dist Folder

 

This folder contains all the frontend related files like JS, CSS etc.

In the CSS & JS folder you will find files named like: application.min.js, vendor-manage.css etc.

For the application 2 types of files are there one is minified (.min) & other one is normal non-minified files (.src). By default, application uses .min files & called in to below named views which are placed under resources/views using __yesset helper functions, which dynamically finds the files on given file named & path contains *.

  • *-master.blade.php
  • includes/head-content.blade.php
  • includes/foot-content.blade.php

media-storage

 

This folder stores all the static media of the files like images etc.

For the most other things you can consider Laravel PHP Framework documents at below link: https://laravel.com/docs/6.x

 

Emails

For some action system uses email by default it uses php mail function as driver you can change it using .env file for more info see https://laravel.com/docs/6.x/mail

System uses resources/views/emails/index.blade.php as main view you can manage header & footer from here. Also, all the email view files are stored in resource/views/email folder.

 

Please Note

There is certain information you should aware of.

  1. Application cache (ServerSide) some queries (settings etc.) are cached for better performance if you think you have made some changes to database directly in the related tables, please consider deleting folders at storage/ framework cache.
    1. If you want to disable these query cache you need to set ENABLE_DB_CACHE=false in the .env file.
  2. If you set APP_DEBUG=true in the .env file. the system also logs lot of information in to the Browser’s Console panel for debugging, so please keep it false for the production uses.
     
  3. When the APP_DEBUG=false in the .env file. the page’s markup automatically minified
  4. Email are sent in English Only.