Hello aaPanel Team,
I am experiencing an issue with Git Manager during deployment.
Environment
aaPanel (latest version)
Laravel application
PHP 8.2
Git Manager deployment
Web server user: www
Issue
Whenever I deploy my Laravel project using Git Manager, all files and folders are automatically set to permission 755 after the deployment completes.
For a Laravel application, the expected permissions are:
Directories: 755
Files: 644
storage/ directories: 775
storage/ files: 664
bootstrap/cache: 775
.env: 600 or 640
However, after every deployment, all files (including PHP files, Composer files, configuration files, etc.) are changed to 755.
Even though my deployment script explicitly runs:
find "$PROJECT_DIR" -type d -exec chmod 755 {} \;
find "$PROJECT_DIR" -type f -exec chmod 644 {} \;
the final permissions remain 755 for both files and directories.
Additional Information
Deployment runs successfully.
The deployment script is executed as root.
The issue occurs only when using Git Manager.
Running the permission commands manually after deployment sets the correct permissions.
It appears that Git Manager changes the permissions after the custom deployment script finishes.
Questions
Is this expected behaviour in Git Manager?
Does Git Manager automatically run a recursive chmod -R 755 after deployment?
Is there a setting to disable this behaviour?
Is this a known bug in the current version of aaPanel?
Any assistance would be appreciated.
Thank you.
