Be able to application specific environments variables or ignore .env / .htaccess on staging push
There is suggestions dating back to 2016,17,18 and 19 to be able to do this but still no working solution?
You are able to do this at other platforms such as at Heroku, AWS, Azure and more.
Else the staging functionality would be pretty useless or at least an hassle to deal with if you need to reset your .env every time before you push your code while using a framework.
I do under stand that the servers are hosted at other services and could be a bit tricky to set env if there apis dosen't support it.But at least add it for those that dose...
Or an other approach would be to add an ignore functionality for specific files such as .env when pushing data.
The .env file and its vars should NEVER be track by git and should ALWAYS be ignored do to it cant include secrets or in laravel/lumens case even passwords.
I was advised by your support to create a php script that calls Cloudways api to trigger the staging push then overwrite my .env after this i done.
This works but still this would not be a valid solution in my opinion do the secrets and passwords has to be hard coded and/or tracked.. Also if you have many applications hosted you also need to create this script for every application you create.