Hi, I would like to report a few issues and typos in the Python Project Manager (seen in aaPanel 8.0.5); not the deprecated plugin, but the native feature. Typo in default venv directory path which is created under /www/server/pyporject_evn/ when you can read "pyporject_evn" instead of (I guess) "pyproject_env". Using the UI to populate the venv with my project's requirements, I saw it looks for "requirement.txt" (singular) instead of the common "requirements.txt" (plural). Packages installed via the UI end up with strict permissions (drwxr-x--- / 750 owned by www:www). As a result, when opening a terminal session with a different user (from SSH client or using the terminal tab of aaPanel), no package can be installed and pip cannot be executed until manually running a chmod -R a+rX on the venv directory. Could you please fix these in the next release? TIA Kind regards,

Hello, thanks for your feedback This is caused by historical issues, and there is currently no plan to deal with it because it will affect existing projects. You can select the corresponding file for manual installation. Based on the permission issues handled by your user, it is recommended that you install dependent libraries on the project. hilord

Hum, sorry, but it sounds weird to me to have a buggy Python management module while aaPanel comes from Python developers, you know 😉 You could move to "pyproject_env" and create symlink for existing projects 🙂 I made it in the terminal activating the venv ^^ A chmod solved the issue. Hoping this part of aaPanel will reach the level of the rest of the panel in the future 😉

Issues and typos in Python Project Manager

hilord

Hi, I would like to report a few issues and typos in the Python Project Manager (seen in aaPanel 8.0.5); not the deprecated plugin, but the native feature.

Typo in default venv directory path which is created under /www/server/pyporject_evn/ when you can read "pyporject_evn" instead of (I guess) "pyproject_env".
Using the UI to populate the venv with my project's requirements, I saw it looks for "requirement.txt" (singular) instead of the common "requirements.txt" (plural).
Packages installed via the UI end up with strict permissions (drwxr-x--- / 750 owned by www:www). As a result, when opening a terminal session with a different user (from SSH client or using the terminal tab of aaPanel), no package can be installed and pip cannot be executed until manually running a chmod -R a+rX on the venv directory.

Could you please fix these in the next release?

TIA
Kind regards,

aaPanel_Kern

Hello,

thanks for your feedback

This is caused by historical issues, and there is currently no plan to deal with it because it will affect existing projects.
You can select the corresponding file for manual installation.
Based on the permission issues handled by your user, it is recommended that you install dependent libraries on the project.

hilord

Hum, sorry, but it sounds weird to me to have a buggy Python management module while aaPanel comes from Python developers, you know 😉

You could move to "pyproject_env" and create symlink for existing projects 🙂
I made it in the terminal activating the venv ^^
A chmod solved the issue.

Hoping this part of aaPanel will reach the level of the rest of the panel in the future 😉