Run glpi installation when bin directory is missing instead of glpi folder
When used in a kubernetes context with a persistent volume storing data for glpi folder, the installer will not run as it tests for the glpi directory and that directory has been created by Kubernetes storage class.
I suggest the bin directory is tested instead of the root of the glpi directory. This way, if a persistent volume has been provided, but glpi has not yet been installed, the installation will still happen. Once it's been completed, the bin directory will exist and installation will not happen.
This will also ensure that new installation is performed when the container is upgrade to a new version as the new container will not contain the bin directory, only the files, plugins, config, and marketplace which are provided as volumes.
Run glpi installation when bin directory is missing instead of glpi folder
When used in a kubernetes context with a persistent volume storing data for glpi folder, the installer will not run as it tests for the glpi directory and that directory has been created by Kubernetes storage class.
I suggest the bin directory is tested instead of the root of the glpi directory. This way, if a persistent volume has been provided, but glpi has not yet been installed, the installation will still happen. Once it's been completed, the bin directory will exist and installation will not happen.
This will also ensure that new installation is performed when the container is upgrade to a new version as the new container will not contain the bin directory, only the files, plugins, config, and marketplace which are provided as volumes.
Example deployment.yaml file below: