Download the PHP package provisionsgroup/config-sync-php without Composer
On this page you can find all versions of the php package provisionsgroup/config-sync-php. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download provisionsgroup/config-sync-php
More information about provisionsgroup/config-sync-php
Files in provisionsgroup/config-sync-php
Package config-sync-php
Short Description Add remote configuration synchronization to Laravel
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 config-sync-php
config-sync
Config Sync is a generic PHP Composer package that can be extended to support multiple backends - where today it only supports HashiCorp Vault - whose purpose is to synchronize a set of backend secrets data to a locally encrypted file. Compared to a typical PHP Laravel apps, the design goals of the Config Sync are to,
- Replace the .env file; especially for secrets
- Replace the ENVIRONMENT variables; especially for secrets
- Decrease coupling for an app when accessing secrets or configuration data from a backend
- Support Kubernetes Pod secrets/configuration bootstrapping while still supporting local development
Prerequisites
- composer
- PHP
- access to somewhere that HashiCorp vault is hosted
- Configuration stored in developer mount in Vault
developerenvironment (see below) will require additional setup in your.envfile
Command
Options
There are four options that can be specified:
Currently, the only option for --backend is vault and the default is vault so it is not required to specify this option when running the command. The code was written in such a way, that should another backend be chosen in the future, as long as it aligns with the interface, it could easily be swapped out in lieu of Vault.
The --environment option has three choices:
localdeveloperkubernetes
local environment
The local environment will create a Config Safe from your local Vault server using the Vault auth token to authenticate and retrieve the secret to create the Config Safe for your local running application.
developer environment
The developer environment will create a Config Safe from your developer mount in Vault. The first time, you will need to add the following to your local .env file:
VAULT_MOUNT=location of Vault mount
VAULT_SECRET=vault secret name
When authenticating with Vault, Config Sync assumes that you will use your LDAP username and password, but this can be changed in the config.
kubernetes environment
The kubernetes environment will create a Config Safe from the Vault in the environment where the applicaiton is running. This will use the JWT (Kubernetes ServiceAccount token) and the role (i.e. auditor-portal) to authenticate with Vault and fetch the secret for that role to create the Config Safe.
