Bruno, we discussed this via email, and I'm entering it as an issue per your request.
It would be nice to have a pre-deploy and post-deploy hook that would let you run a script of your choosing (in this case, modifying/transforming configuration files prior to pushing them to production).
You could even make a per-file pre-deploy hook that'd call the script with the filename/contents, so you'd just have to check the filename, and if it was Laravel's .env config file for example, you could change its contents by transforming it or copying over a new config from a folder name, perhaps one that matches your git-deploy ini file name.
Bruno, we discussed this via email, and I'm entering it as an issue per your request.
It would be nice to have a pre-deploy and post-deploy hook that would let you run a script of your choosing (in this case, modifying/transforming configuration files prior to pushing them to production).
You could even make a per-file pre-deploy hook that'd call the script with the filename/contents, so you'd just have to check the filename, and if it was Laravel's .env config file for example, you could change its contents by transforming it or copying over a new config from a folder name, perhaps one that matches your git-deploy ini file name.