Download the PHP package beyondcode/laravel-credentials without Composer
On this page you can find all versions of the php package beyondcode/laravel-credentials. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download beyondcode/laravel-credentials
More information about beyondcode/laravel-credentials
Files in beyondcode/laravel-credentials
Package laravel-credentials
Short Description Store and access encrypted credentials in your Laravel application.
License MIT
Homepage https://github.com/beyondcode/laravel-credentials
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 laravel-credentials
Add encrypted credentials to your Laravel production environment
The beyondcode/laravel-credentials package allows you to store all your secret credentials in an encrypted file and put that file into version control instead of
having to add multiple credentials into your .env file in your production environment.
There are a couple of benefits of using encrypted credentials instead of environment keys:
- Your credentials are encrypted. No one will be able to read your credentials without the key.
- The encrypted credentials are saved in your repository. You'll have a history of the changes and who made them.
- You can deploy credentials together with your code.
- All secrets are in one location. Instead of managing multiple environment variables, everything is in one file.
Here's how you can access your stored credentials. In this example we're retrieving the decrypted credential for the key api-password:
You can also specify a fallback value to be used if the credential for the specified key cannot be decrypted:
With the built-in edit command, you can easily edit your existing credentials. They will be automatically encrypted after saving your changes.
Optionally, you can change the used editor by adding the following to your .env file:
Installation
You can install the package via composer:
The package will automatically register itself.
You can optionally publish the configuration with:
This is the content of the published config file:
Testing
Changelog
Please see CHANGELOG for more information on what has changed recently.
Contributing
Please see CONTRIBUTING for details.
Security
If you discover any security related issues, please email [email protected] instead of using the issue tracker.
Credits
- Marcel Pociot
- All Contributors
License
The MIT License (MIT). Please see License File for more information.
