Download the PHP package techins-software/laravel-boilerplace without Composer

On this page you can find all versions of the php package techins-software/laravel-boilerplace. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of techins-software/laravel-boilerplace

Informations about the package laravel-boilerplace

Laravel Boilerplate

This is a boileplace code for admin panels used by our projects. It contains basic views and login functionality alongside with the nessesary files for deployment and testing. Upon frontend bootstrap is used.

Create project:

Setup php dependencies

Create the nessesary .env file. If using our docker solution use the .env.php_dev:

NOTE these credentials are viable if using the docker solution. It should NOT be used upon production

Then once .env is generated run:

Build Frontend

For development you can run:

For onetime builds (or ci/cd ones) run:

Github actions & CI/CD

The actions are used for:

  1. Automated Tagging
  2. Running Unit tests upon PR

Look at .github/workflows folder for more info.

Deployment & Building for release upon Server (CI/CD)

It contains, the following basic files for building the AWS codepipeline. Also it contains the following files for deployment:

Also upon build the following files exist:

Any secret values are and should be replaced upon buildspec.yml

View templates

All pages available for logged in users extend the layout.layout-common blade template. In case user is admin you can extend the layout.layout-admin one (it extends the layout.layout-common one placing nessesary links upon header). Feel free to place extra views and modify them as needed.

The layout.fullpage is a layout that does NOT contain any header but only a single main item located as the center of the page, usefull for login and registration pages.

Both layout.layout-common and layout.fullpage contain these sections you can place the nessesary html if needed:

All templates use bootstrap and fontawesome.

Javascript

All layouts extending layout.layout-common, by default load the js/default.js file. In case that a custom javascript file is needed then place the appropriate js file upon resources/js and upon the blade template and override the js section, look examples bellow.

Example 1: overriding the default js with resources/js/myjs.js

Example 2: Loading resources/js/myjs.js alongside the default js

Css

There are the following css loaded bty Default upon each template:

In case you want to include your own css follow these steps:

Create css files

First create the nessesary css file upon resources/css. Then place inside inside the following:

Load 3rtd party css

Furthermore if using a fullpage layout and want to place extra css on it you can do it:

You can use @import to import any 3rd party css as well if needed. Is css is installed via npm ensure that is placed upon vite.config.js file: https://github.com/TechIns-Software/laravel-boilerplace/blob/6331fb7a1b9238f8e9f193c80e872f116b90245c/vite.config.js#L40-L52

Load upon blade

Either case once you have your css ready you can load the file (assuming named as resources/css/mycss.css):

Build frontend

Then you can build the frontend as mentioned above:

All versions of laravel-boilerplace with dependencies

PHP Build Version
Package Version
Requires php Version ^8.2
laravel/framework Version ^11.9
laravel/tinker Version ^2.9
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package techins-software/laravel-boilerplace contains the following files

Loading the files please wait ...