Adrian
My feedback
3 results found
-
34 votesAdrian
supported this idea
·
An error occurred while saving the comment An error occurred while saving the comment Adrian
commented
It is frankly bizarre to me that there is no per-application environment file editor as we see in Laravel Forge. This would then be included in the virtual host for that application so the variables are available to it.
Putting API keys and so on in the source code is not an option.
This is a critical feature, and without it I will not be able to migrate my clients' applications to Cloudways as I had hoped.
-
8 votesAdrian
supported this idea
·
-
79 votesAdrian
supported this idea
·
@cloudways
RE: "As you rightly point out, this functionality is available and possible through the PHP Settings feature provided on the Platform."
This seems to be false information. None of the following are allowed by the PHP FPM Settings editor:
;env[KEY] = VALUE
;VAR_NAME=VALUE
env[KEY] = VALUE
VAR_NAME=VALUE
It just says "One or more directive are not supported. Please choose from php_flag, php_admin_flag, php_value and php_admin_value."
How do we set variables here?
I have been advised to use the .bashrc file to load them. But then these are not application-specific and also .bashrc is not editable. Its permissions are set to 640 but vim says "Cannot open file for writing".
So that is not possible either.
It seems there is no solution because Cloudways have blocked every approach.