Download the PHP package dex/frontier without Composer
On this page you can find all versions of the php package dex/frontier. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Package frontier
Short Description The frontier between your Laravel app and your decoupled frontend
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 frontier
Frontier
The frontier between your Laravel app and your decoupled frontend.
Frontier allows you to run your favorite frontend framework and to serve the initial page by the backend, like a proxy.
It's great for anyone using custom domains to test their applications or running multiple frontends that use the same backend. You will be able to test your app using cookies, sessions and avoiding CORS "same source" issues.
Installation
Just install dex/frontier into your Laravel app and configure some
environment variables.
Environment variables
You can configure your frontend using some environment variables described below.
| Variable | Description | Default |
|---|---|---|
FRONTIER_TYPE |
Define type of controller http, proxy or view |
view |
FRONTIER_ENDPOINT |
Endpoint where the frontend will run | frontier |
FRONTIER_VIEW |
Default view that will be rendered or url of the server |
frontier::index |
FRONTIER_VIEWS_PATH |
Directory where all the views are |
frontier/resources/html |
FRONTIER_FIND |
Content that will be replaced | |
FRONTIER_REPLACE_WITH |
Content that will be the replacement | |
FRONTIER_PROXY |
URIs that you will do proxy | |
FRONTIER_CACHE |
When http type, indicates se cache will be do |
true |
FRONTIER_PROXY_HOST |
url of the assets server |
|
FRONTIER_PROXY_RULES |
Proxy rules |
Frontend types
You can use 3 different types of frontend http, proxy or view.
HTTP
Use in FRONTIER_VIEW the URL of your frontend server.
Proxy
Use in FRONTIER_PROXY_HOST or FRONTIER_VIEW the URL of your frontend server.
FRONTIER_VIEWwill be removed in the future.
View
Use in FRONTIER_VIEW the name of your view that you initialize your frontend, this is relative a Blade views.
Examples
Vite and Vue.js
When using Vite and Vue.js you can start your project with these
environment variables using http approach.
Nuxt.js
When using Nuxt you can start your project with these environment variables using proxy approach.
Multiple frontends
You can run multiple frontends, just create a custom configuration file.
The config/frontier.php file will be created in your Laravel app. This file contains some settings that can be
replicated to add more frontends to your app.
License
Frontier is licensed under the MIT license. See the license file for more details.
All versions of frontier with dependencies
illuminate/http Version ^9|^10|^11
illuminate/support Version ^9|^10|^11
illuminate/view Version ^9|^10|^11