Configuration files

Most web applications rely on configuration files to define settings that are specific to the server they're running on.

For example:

• Laravel uses .env for database credentials, mail settings and other environment-specific configuration
• WordPress uses wp-config.php for database credentials and other application settings

Launchdeck lets you manage these configuration files on a per-server basis and automatically include them when deploying a new release.

Adding configuration files

You can add configuration files from the server settings in your Launchdeck project.

Upload a file using drag-and-drop, or enter its contents directly using the built-in editor.

How configuration files are deployed

Configuration files are added to each release after your build commands have finished running.

If you update a configuration file, create a new build for the changes to take effect. You can use the Retry button to rebuild your latest release.

Configuration file paths can include subdirectories. If a directory doesn't already exist in the release, Launchdeck will create it automatically (similar to mkdir -p).

For larger or binary files that need to persist between deployments — such as user uploads — use shared paths instead. See the build automation guide for details.

Happy deploying!