Download the PHP package newridetech/silicon without Composer

On this page you can find all versions of the php package newridetech/silicon. 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?

Informations about the package silicon

Silicon Framework

In the era of growing number of regulations, privacy awareness and security restrictions we felt like it was a good time to introduce the new and responsible approach to handle sensible data while developing custom tailored solutions. Our goal is to handle good security and privacy management practices and to do it in a way the will make app development and maintenance simpler instead of making it harder or more complicated.

Silicon can be viewed as a glue layer between Laravel and Keycloak. Those technologies combined provide every required aspect to handle application security, identity management and ease of development. It is simple to develop new features and maintain the app and most probably Silicon will boost your performance but it's not aimed at everyone, especially not at coding beginners.

Silicon does not reinvent concepts, it just stands on shoulders of giants. What it provides is the separation of concerns and modular Laravel code divided into bundles with security and identity management concepts included by design. It would probably require some effort (although it's possible) to include Silicon into an existing project but if you are thinking about creating a fresh codebase or new API / webapp version it may be a choice worth considering.

Core benefits

Caveats

How it works

Silicon provides several built-in services that introduce security oriented code bundles into Laravel. Concept is somewhat similar to the Symfony bundle system. In Symfony world those are considered a legacy feature (for a good reason), but in Silicon they play different role than just separation of concerns thus they are still relevant and innovative.

Each bundle (or extensions - as they are called in Silicon world) besides a service provider provide entry point class that extends base Newride\Silicon\bundles\extensions\Extension. In their essence, bundles are automatically registered Laravel packages with built-in additional Silicon features. Extension is the place to register Laravel policies and provide simple entry point to check if user has sufficient permissions to use the entire bundle. Users are not stored in the application database, they are retrieved by using Keycloak's OAuth access token.

Good practice is to assign a different role to each bundle to easily build and maintain modular application. For example if your app consist of blog and shop you can have two extensions: shop and blog and view-shop, view-blog roles respectively. Extension entry point should make one or two generic checks to cut off access to the extension completely. More specific permissions, access control lists etc should be moved to Laravel's security policies.

Given such basic code organisation, your application would not store any personal data and be divided into modules with several layers of flexible security checks.


All versions of silicon with dependencies

PHP Build Version
Package Version
Requires alsofronie/eloquent-uuid Version ^1.0
doctrine/dbal Version ^2.7
erusev/parsedown Version ^1.7
felixkiss/uniquewith-validator Version ^3.1
fideloper/proxy Version ^4.0
laravel/framework Version 5.7.*
laravel/tinker Version ^1.0
laravelcollective/html Version ^5.6
leafo/scssphp Version ^0.7.6
league/oauth2-client Version ^2.3
league/uri Version ^5.3
newridetech/laravel-scss Version ^1.2
newridetech/php-classnames Version ^1.2
php Version ^7.1.3
pviojo/oauth2-keycloak Version ^2.0
watson/validating Version ^3.1
webmozart/assert Version ^1.3
webmozart/glob Version ^4.1
wikimedia/composer-merge-plugin Version ^1.4
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 newridetech/silicon contains the following files

Loading the files please wait ....