is a configuration pattern that loads environment variables from a
.env file. Amezmo generates a
.env file for you at instance creation time.
This file is automatically available to you from your webroot.
Depending on the options you've chosen at instance creation time, you will see a set of predefined variables.
When a new deployment happens, the most recent
.env file is copied into your deployments
target release directory.
Amezmo automatically generates a
.env file for you when you launch an instance.
You can edit this file at anytime from the Configuration page.
Upon updating your configuration from the dashboard, the updates are immediately copied into your current release directory. Amezmo does not validate your file before placing it inside the root of your current release directory tree.
Your workers are reloaded via SIGHUP after your configuration file is copied into your release directory.
The following variables are automatically generated for you when you launch an instance.
||The hostname of the application environment|
||Path to the persistent storage directory|
||This path can be used to persist log file across deployments|
||Contains the application environment name|
||The environment name|
Amezmo provides the following database variables if your instance has MySQL installed.
||Database username that was provided during instance creation|
||Contains the hostname of your MySQL server|
||Default database name|
||The version number of MySQL in major.minor.patch form|
Amezmo provides the following Redis variables if your instance has Redis installed.
||The redis server IP address or hostname|
Upon updating your configuration file, Amezmo will optionally execute a script on your behalf.
||This script is executed before Amezmo places the updated configuration file into your current release directory|
||This script is executed after the file was successfully copied to your current release directory, but before your workers are reloaded.|
- Configuration hooks have a 15 second timeout.