Would it be possible to standardize the enviroments more in terms of defaults, e.g. naming of databases, credentials, and so on as well as the handling of the webroot and the .env files.
With regard to the defaults for the databases and other credentials, such as backend credentials via bootstapping, it would be easiest if the user and password are always "reward" or "rewardenv". In addition, the database names should correspond to the enviroment name (reward_env_name).
This would be uniform for all enviroments and would be easier to remember.
In addition, handling the enviroments with the webroot is unattractive because, depending on the enviroment type,
sometimes the .env is contained in the actual project, sometimes it is outside the project or sometimes an .env contains both the application configuration and the reward configuration.
My suggestion would be to either rename the reward .env file to e.g. .env.reward or move it to the .reward directory in the project, so that the collision with the project .env files is avoided.
Would it be possible to standardize the enviroments more in terms of defaults, e.g. naming of databases, credentials, and so on as well as the handling of the webroot and the .env files.
With regard to the defaults for the databases and other credentials, such as backend credentials via bootstapping, it would be easiest if the user and password are always "reward" or "rewardenv". In addition, the database names should correspond to the enviroment name (reward_env_name).
This would be uniform for all enviroments and would be easier to remember.
In addition, handling the enviroments with the webroot is unattractive because, depending on the enviroment type,
sometimes the .env is contained in the actual project, sometimes it is outside the project or sometimes an .env contains both the application configuration and the reward configuration.
My suggestion would be to either rename the reward .env file to e.g. .env.reward or move it to the .reward directory in the project, so that the collision with the project .env files is avoided.