Download the PHP package engageinteractive/laravel-frontend without Composer
On this page you can find all versions of the php package engageinteractive/laravel-frontend. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download engageinteractive/laravel-frontend
More information about engageinteractive/laravel-frontend
Files in engageinteractive/laravel-frontend
Package laravel-frontend
Short Description Frontend build framework for Laravel projects
License MIT
FAQ
Example:
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 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.
Informations about the package laravel-frontend
Laravel package to provide frontend template routes for non-production environments.
Installation
The package's service provider will be autoloaded on startup.
Next publish the templates and config file:
The files published this way are examples of structure and are not enforced by the package. Edit config/frontend.php to change the paths of these files. If you also need to change the filename of config/frontend.php see Config File Customisation.
Basic Usage
Add the following key to your .env file to enable the frontend routes (typically, local and staging):
If this key is already in use for your project, you can change this in the config/frontend.php file.
Now you can visit /frontend/ and see the templates.
Page Defaults
Often within an app, it is useful to have view composers that load fallback variables from a configuration or the database when not provided by the controller explicitly. An example of this could be the page title in the HTML <head> for example. Depending on the setup you might not have a database defined when building the frontend templates, or you might not even want the database involved. In this case you still want your layout templates to recieve this variables, but it would be nice to hard code them for all the frontend templates.
To do this you can subclass the PageDefaultsViewComposer and add register it within a service provider:
Subclass the View Composer implementing your own values
Register your View Composer
Config File Customisation
By default the package uses the config/frontend.php file to define all the settings, such as route name, URL path, template file paths etc. However, the package uses Laravel Config Provider to allow you change to which file is used. To do so bind your own instance of ConfigProvider in your AppServiceProvider. This is useful in cases where config/example-package.php is already in use within your project for example.
First create your own provider:
Then, add the provider to your bindings on startup.
Now, throughout the package when the ConfigProvider is requested via the Laravel service container, yours will be created instead.
Laravel Compatibility
Works on Laravel 5.5, 5.6 and 5.7.
License
Laravel Frontend is open-sourced software licensed under the MIT license.
