Download the PHP package skyzyx/signer without Composer
On this page you can find all versions of the php package skyzyx/signer. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download skyzyx/signer
More information about skyzyx/signer
Files in skyzyx/signer
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 signer
Signer
The Signer class is designed for those who are signing data on behalf of a public-private keypair.
In principle, the "client party" has public key (i.e., client_id) and a matching private key (i.e., client_secret) that can be verified by both the signer and the client (but nobody else as we don't want to make forgeries possible).
The "signing party" has a simple identifier which acts as an additional piece of entropy in the algorithm, and can help differentiate between multiple signing parties if the client party does something like try to use the same public-private keypair independently of a signing party (as is common with GPG signing).
Based on a simplified version of the AWS Signature v4.
Examples
Installation
Using Composer:
And include it in your scripts:
Testing
Firstly, run composer install -o to download and install the dependencies.
You can run the tests as follows:
Debug Logging
NOTE: You should only use logging during development — never in production.
Signer implements the PSR-3 Psr\Log\LoggerAwareInterface. Because of this,
you can inject any PSR-3-compatible logging package, and Signer will use it to log DEBUG-level messages.
API Reference
The API Reference is generated by a tool called phpDocumentor 2.x. You should install it locally on your system with:
Once it's installed, you can generate updated documentation by running the following command in the root of the repository.
Contributing
Here's the process for contributing:
- Fork Signer to your GitHub account.
- Clone your GitHub copy of the repository into your local workspace.
- Write code, fix bugs, and add tests with 100% code coverage.
- Commit your changes to your local workspace and push them up to your GitHub copy.
- You submit a GitHub pull request with a description of what the change is.
- The contribution is reviewed. Maybe there will be some banter back-and-forth in the comments.
- If all goes well, your pull request will be accepted and your changes are merged in.
Authors, Copyright & Licensing
- Copyright (c) 2011-2014 Amazon Web Services, Inc.
- Copyright (c) 2014 Ryan Parman.
See also the list of contributors who participated in this project.
Licensed for use under the terms of the Apache 2.0 license.
Coding Standards
PSR-0/1/2 are a solid foundation, but are not an entire coding style by themselves. I have taken the time to document all of the nitpicky patterns and nuances of my personal coding style. It goes well-beyond brace placement and tabs vs. spaces to cover topics such as docblock annotations, ternary operations and which variation of English to use. It aims for thoroughness and pedanticism over hoping that we can all get along.
