Download the PHP package flyo/nitro-laravel without Composer

On this page you can find all versions of the php package flyo/nitro-laravel. 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 flyo/nitro-laravel

Informations about the package nitro-laravel

Flyo Nitro Laravel Framework Module

publish the config

Adjust the token in config/flyo.php

Ensure to remove the default routes in routes/web.php which could conflict with the cms routes.

Views

Add/Adjust the cms.blade.php view file in resources/views, this is where the cms page loader starts:

Now all component block views are looked up in ressources/views/flyo, for example if you have a Flyo Nitro component block with name Text the view file would be ressources/views/flyo/Text.blade.php utilizing the following variables:

You can adjust the views namespace in the config file using views_namespace key.

To make the block editable (which means clicking in the block, will correctly add the block to the cms editor) you can use the following blade directive @editable($block):

Layout Variable

In order to build menus, the $config response from the api is a global available variable, for example this could be used in layout-components:

Make sure to include the <x-flyo::head> component in the head of your layout file, for example

This will add needed javascript for reloading and editin blocks in local environments and also assign all available meta informations.

A full layout example which could be placed in resources/views/layouts/app.blade.php:

Entity Detail

To display an entity detail page, you have to register a route, create a controller and a view file:

Routing File example

The Controller:

And the example tier.blade.php in the resources/views folder:

There is also a more generic controller available which can be used to display any entity detail page:

where the poi.blade.php file in the resources/views folder could look like this:

Multilanguage

The requests will pass the configured APP_LOCALE (which is used in laravel for localization) to the flyo api.

Defined the available locales in the config/flyo.php file:

The ServiceProvider will check for segments /de, /en in the url and set the locale in the request object if the locale is available in the config file.

Pass the language for entity Detail Requests:

 Misc

In order to resolve the Configuration object somewhere in your application, you can use the following code:

Same for the page response

Documentation

Read More in the Docs

Package Development

  1. Check the example-app/.env file to have a correct flyo token.
  2. Go to example-app and run php artisan serve to get the example app running.

All versions of nitro-laravel with dependencies

PHP Build Version
Package Version
Requires flyo/nitro-php Version ^1.1
laravel/framework Version ^11|^12
flyo/nitro-php-bridge Version ^1.2
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 flyo/nitro-laravel contains the following files

Loading the files please wait ....