Download the PHP package nandi95/laravel-env-in-aws-ssm without Composer
On this page you can find all versions of the php package nandi95/laravel-env-in-aws-ssm. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download nandi95/laravel-env-in-aws-ssm
More information about nandi95/laravel-env-in-aws-ssm
Files in nandi95/laravel-env-in-aws-ssm
Package laravel-env-in-aws-ssm
Short Description Manage your environment variables in AWS' SSM Parameter store
License MIT
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-env-in-aws-ssm
laravel-env-in-aws-ssm
Manage your environment variables in in AWS' SSM Parameter store
Download or upload your .env files into the free AWS's SSM store. This allows you to store up to 10,000 keys over your aws account in each region. More keys are available subject to your quota.
This provides a good companion to referencing env values in cloudformation, serverless framework or to download within runners in other forms of Continuous Deployment processes.
This package provides two commands:
Arguments:
-
stage- this is something the equivalent ofproduction|staging|develop|...) which identifies what environment the variables are used in. -
--appName=(optional) - this is the name of the current app (equivalent the APP_NAME in the.envfile normally). If not given, or cannot be found, it will prompt the user for it. -
--secretKey=(optional) - The secret key for the user with the required permissions. If not given, or cannot be found, it will prompt the user for it. -
--accessKey=(optional) - The access key id for the user with the required permissions. If not given, or cannot be found, it will prompt the user for it. -
--region=(optional) - The region the infrastructure resides in. If not given, or cannot be found, it will prompt the user for it. --decrypt(optional | Default: false) - Decrypt the values before pulling them.See more details about encrypt in the AWS documentation
All commands will use the env file respective to the stage argument. For example: with stage argument production it will work with the .env.production file. If the file exists when pulling, it will back up the existing file.
Parameter <-> environment variable
Keys are transformed in the following manner:
DB_PASSWORD => {appName}/{stage}/DB_PASSWORD
