Laravel environment after deploy alway dev but in overlays/.env another

[yuriizee]

When a command is executed
dploy deploy main
and you have your own overlays/.env file that specifies any APP_ENV value, then it is ignored.
Deploy will always be dev in the cached laravel configuration file, even though the same .env file will have a different value.

STR:

1. Setup Laravel project
2. Configure dploy and overlays/.env for project with APP_ENV=production value, with before_commands cd {release_directory} && php8.3 artisan optimize:clear
3. run dploy deploy main

Temp solution: run dploy deploy main --env=production

[yuriizee]

@cloudpanel-io

[cloudpanel-io]

Can you get in touch with me (Stefan Wieczorek) on our Discord?

https://discord.cloudpanel.io/

I want to discuss it with you there.

[umizoomi]

For others who are also running against this. Its probably because you want to have .env.dev / .env.local in your repo. In that case, add this to the ~/.dploy/config.yml before_commands list

- 'cd {release_directory} && rm -f .env.dev && rm -f .env.local'

[holaa2019]

I still have the "dev" as App_ENV. After deploying laravel with my own .env in the overlays folder, my .env file shows up in the current.
But if I php artisan tinker and ask for config('app.env') I get 'dev'

This is regardless of having - 'cd {release_directory} && rm -f .env.dev && rm -f .env.local'
in the before and after commands.

I believe the 'dev' is coming from the .env.local in the dploy repo which has APP_ENV=dev

Was trying to figure out, if I am using it wrongly by using dploy deploy master, but couldn't see anything in the dploy repo.

So, I created a script (replace REPO-NAME with yours), which runs config:clear and config:cache after the deploy script finished its work, than I get the production environment and debug=false as it should. My impression is that the dploy script uses the .env.local and loads it into its own Kernel and ignores the settings from my own overlay .env file as long as it runs. Other than that cloudpanel and dploy are fantastic!

#!/bin/bash

BRANCH="${1:-master}"

dploy deploy "$BRANCH"

APP_DIR="./htdocs/REPO-NAME/current"

# If APP_DIR is set, change to that directory
if [ -n "$APP_DIR" ]; then
  cd "$APP_DIR" || { echo "Directory $APP_DIR not found"; exit 1; }
fi

php artisan config:clear
if [ $? -ne 0 ]; then
  echo "Failed to clear config cache"
  exit 1
fi

php artisan config:cache
if [ $? -ne 0 ]; then
  echo "Failed to cache config"
  exit 1
fi

echo "Config cache cleared and rebuilt successfully."