LOG, but SES for environments with the name production Vanity domain, or custom domain if existsĭynamoDB, or cache (Redis) resource if existsĭatabase (MySQL, Postgresql, etc) resource if exists Here is the full list of environment variables injected by Vapor on your environment. As an example, by adding a cache or database key to your vapor.yml file, Vapor will inject the necessary CACHE_* and DB_* environment variables. Vapor automatically injects a variety of environment variables based on your environment's configured cache, database, etc. # Creating EnvironmentsĮnvironments may be created using the env Vapor CLI command:Įnvironments : production : build : - 'composer install -no-dev' my-environment : build : - 'composer install -no-dev' # Environment VariablesĮach environment contains a set of environment variables that provide crucial information to your application during execution, just like the variables present in your application's local. However, don't be afraid to create more environments for testing new features without interrupting your main staging environment. Typically, you will have an environment for "production", and a "staging" environment for testing your application. Each project may have as many environments as needed. All of your deployments and invoked commands are stored within environments.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |