Download the PHP package uteq/signature without Composer
On this page you can find all versions of the php package uteq/signature. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download uteq/signature
More information about uteq/signature
Files in uteq/signature
Package signature
Short Description A Package that gives the ability to create (temporary) links for usage on websites, emails and more
License MIT
Homepage https://github.com/uteq/signature
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 signature
Signature
This laravel package gives you the ability to create action links that can be used everywhere on your site (including emails).
A simple url can be created by the example below. The first parameter is the class to execute the action when the user visits the link, the second parameter is an array that holds all the data to be provided to the action class. The payload automatically gets encrypted when entering the database.
The get() function returns a complete url based on the APP_URL in the .env file and the 'action_route' in the signature config
Example action class:
Installation
You can install the package via composer:
You can publish and run the migrations with:
You can publish the config file with:
This is the contents of the published config file:
Usage
You can create a link with the examples provided below. All options are optional and can be used independently.
- payload(): Alternative way to pass variables to the link
- expirationDate(): Option to allow you to specify the expiration date (defaults to 2 weeks from creating the link)
- password(): Protects the link by asking for the password set in this function when using the link
- oneTimeLink(): Deletes the link when the action has successfully executed
-
get(): Makes a complete url based on the APP_URL in the .env file and the 'action_route' in the signature config (defaults to /action/{key})
- longerKey(): uses a longer key in the url with changeable length (max. 254). This is recommended when handling sensitive data.
-
group(): groups signatures together via the string given to the function, when a signature is deleted, all signatures with the same group also get deleted.
- customKey(): grants the ability to use a custom key, if both longerKey() and customKey() are used in the same signature, the last function will override the other.
Action class:
Commands
This command deletes all the signatures that have expired.
Testing
Changelog
Please see CHANGELOG for more information on what has changed recently.
Contributing
Please see CONTRIBUTING for details.
Security Vulnerabilities
Please review our security policy on how to report security vulnerabilities.
Credits
- Stef van den Berg
- Nathan Jansen
- All Contributors
License
The MIT License (MIT). Please see License File for more information.
All versions of signature with dependencies
ext-json Version *
ext-openssl Version *