Download the PHP package romanzipp/laravel-blockade without Composer

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

Laravel Blockade

Latest Stable Version Total Downloads License GitHub Build Status

A simple but highly customizable package for preventing access to private or WIP Laravel projects.

Features

Why just not use the Laravel Maintenance Mode?

Blockade offers a simple way to share access to development or staging environments only by typing in a password. The authenticating user will return the intended URL after a successful login. The built in Laravel Maintenance Mode uses a different approach by denying access in deployment or maintenance procedures.

Do we need yet another access control package?

Yes! From my experience, other maintenance mode packages (and similar) only rely on one authentication method which is either cookie or session based. When working on many projects with different tech stacks, some drivers like session storage in API-only projects are simply not available. Blockade is meant to solve this issue by combining several auth mechanisms in one package.

Installation

Configuration

Copy configuration & assets files to project folder:

You can also publish views (--views) and language files (--lang) to further customize the Blockade template.

Make use of the --update parameter if you are seeing an error message at the bottom.

Usage

To enable Blockade, simply

  1. Set the environment variables BLOCKADE_ENABLED=true & BLOCKADE_PASSWORD=
  2. Register the BlockadeMiddleware class in your middleware stack.

The package defaults to the provided view for password prompt and stores the authentication hash in a cookie.

To reset previous granted access, just change the BLOCKADE_PASSWORD entry. All issued access tokens will be invalid on the next page request.

Handlers

Handlers are responsible for validating authentication requests and sending successful or failed responses. You can set the active handler in blockade.handlers.* config entries.

Handler Description Class
Form (default) The password is provided by a form romanzipp\Blockade\Handlers\FormHandler
Query Parameter The password is attached as query parameter romanzipp\Blockade\Handlers\QueryParameterHandler

Stores

Stores are storing (how surprising) the authentication state for later requests. You can set the active store in blockade.stores.* config entries.

Store Description Class
Cookies (default) The password hash will be stored as browser cookie romanzipp\Blockade\Stores\CookieStore
Session The password hash will be stored in the active session romanzipp\Blockade\Stores\SessionStore

Important: If you are using the SessionStore make sure the BlockadeMiddleware is appended after the Illuminate\Session\Middleware\StartSession middleware.

Extending

You can create your own authentication process by simply implementing the

Assets

It is recommended to publish the provided css files via the unkpg.com and display an error notice in the footer section.

Use the --update argument to update the published assets.

Disclamer

This is no cryptographically secure authentication

The package stores the authentication token as SHA 256 hash of the configured password.

Testing

Build Frontend

Development

Production

Credits

Special thanks to Katerina Limpitsouni for the awesome unDraw SVG illustrations!


All versions of laravel-blockade with dependencies

PHP Build Version
Package Version
Requires php Version ^7.1|^8.0
ext-json Version *
illuminate/console Version ^5.5|^6.0|^7.0|^8.0|^9.0|^10.0
illuminate/support Version ^5.5|^6.0|^7.0|^8.0|^9.0|^10.0
spatie/url Version ^1.3
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 romanzipp/laravel-blockade contains the following files

Loading the files please wait ....