DjangoBlog project address: https://github.com/liangliangyy/DjangoBlog 1.First install the git tool to clone the DjangoBlog project: RedHat|CentOS： yum install git -y Debian|Ubuntu： apt-get update apt-get install git -y Clone the DjangoBlog project: cd /www/wwwroot/ git clone https://github.com/liangliangyy/DjangoBlog 2.Install Python 3.8.12 3.Add DjangoBlog project Parameter Description: Name：Give your project a name Path：Select the root directory of the project,Select the previously cloned directory Version：Choose the python version your project needs,Choose Python Version 3.8.12 here Framework：The project project framework, my project here is Flask, so choose django Startup mode：Choose gunicorn here, You can switch other options according to your needs startuo file/dir：diango select the project directory to start Port：DjangoBlog defaults to 8000 Run user：Start with root privileges Install module now：When adding a project, install the required modules according to the documentation of the project root directory requirements.txt. Start with the sys：Configure startup for the project When we finish project creation, we can’t open the project normally.We need to initialize the project After the installation is complete, the display is as follows: 4.Create a database for the DjangoBlog project When creating, you need to pay attention to selecting the character set: utf8mb4 5.Modify the DjangoBlog configuration: Go to the DjangoBlog directory, enter the djangoblog directory, and modify the configuration file: settings.py After commenting the original database, then add the following content, pay attention to modify it to your database name, user name, password, pay attention to the case of the database. /www/wwwroot/DjangoBlog/djangoblog DATABASES = { 'default': { 'ENGINE': 'django.db.backends.mysql', 'NAME': 'djangoblog_test', 'USER': 'DjangoBlog_test', 'PASSWORD': 'P4KajxAhfJ6dMWph', 'HOST': 'localhost', 'PORT': 3306, 'OPTIONS': {'charset': 'utf8mb4'}, } } if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } Comment the configuration below, otherwise it will cause database errors later, only keep: TIME_ZONE = 'Asia/Shanghai' #LANGUAGE_CODE = 'zh-hans' (English will be displayed after adding annotations) #USE_I18N = True #USE_L10N = True #USE_TZ = True configuration on the project The Python project env used by the project Please replace "8658305af42d6efded53c296d677d3ba_venv" with your project env and execute the command. 6.Start performing data migration Generate data: /www/wwwroot/DjangoBlog/8658305af42d6efded53c296d677d3ba_venv/bin/python3 manage.py makemigrations /www/wwwroot/DjangoBlog/8658305af42d6efded53c296d677d3ba_venv/bin/python3 manage.py migrate Generate super user: (create an administrator user according to the prompt) /www/wwwroot/DjangoBlog/8658305af42d6efded53c296d677d3ba_venv/bin/python3 manage.py createsuperuser Generate test data: /www/wwwroot/DjangoBlog/8658305af42d6efded53c296d677d3ba_venv/bin/python3 manage.py create_testdata Collect static files： /www/wwwroot/DjangoBlog/8658305af42d6efded53c296d677d3ba_venv/bin/python3 manage.py collectstatic --noinput /www/wwwroot/DjangoBlog/8658305af42d6efded53c296d677d3ba_venv/bin/python3 manage.py compress --force Restart the DjangoBlog project 7.The port 8000 used by DjangoBlog is released in Security try to access Open the browser: http://127.0.0.1:8000/ and you can see the effect Replace the ip address with your server address. 8.Map the DjangoBlog project to a web service (nginx/apache), and nginx/apache is responsible for forwarding the request to our Python project on the backend 9.Static file configuration Add the following to site config URL rewrite: location /static/ { alias /www/wwwroot/DjangoBlog/collectedstatic/; expires max; access_log off; log_not_found off; } location /media { alias /www/wwwroot/DjangoBlog/uploads/; expires max; } location ~ \.py$ { return 403; } if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } 10.DjangoBlog project deploys SSL Access effect: Login background error after deploying SSL: https://129djangoblog.com/admin Solution: Modify the configuration file: /www/wwwroot/DjangoBlog/djangoblog/settings.py ALLOWED_HOSTS = ['*', '127.0.0.1', '129djangoblog.com'] # django 4.0新增配置 CSRF_TRUSTED_ORIGINS = ['https://129djangoblog.com'] Replace 129djangoblog.com with your domain name, then go to Python Manager to restart the DjangoBlog project. References: https://github.com/liangliangyy/DjangoBlog/blob/master/docs/README-en.md https://www.bt.cn/bbs/thread-90005-1-1.html

Hi, thanks again for your effort, its very dificult to find documentation about python+django+aapanel (sorry about my english) 😉 I almost finished the tutorial, but I get this:

javierleonet Comment the configuration below, otherwise it will cause database errors later, only keep: TIME_ZONE = 'Asia/Shanghai' #LANGUAGE_CODE = 'zh-hans' (English will be displayed after adding annotations) #USE_I18N = True #USE_L10N = True #USE_TZ = True

javierleonet Hello, is to add a comment and add a # in front of it

Excellent! Sorry, sometimes the ignorance make us blind

aaPanel_Kern please I want to learn django. Where do I get to learn fast

aaP_Utibe2193 Hello, it is recommended to use a search engine to find relevant resources.

aaPanel_Kern Comment the configuration below, otherwise it will cause database errors later, only keep: TIME_ZONE = 'Asia/Shanghai' #LANGUAGE_CODE = 'zh-hans' (English will be displayed after adding annotations) #USE_I18N = True #USE_L10N = True #USE_TZ = True Can you please explain why this is the case? If I am deploying production projects, I may have to use different time zones and I may need TimeZone conversion. Why should I disable those and set the time zone to Shanghai?

Python Manager Deploy Djangoblog

Vladmin-Server

Traceback (most recent call last):
  File "/www/wwwroot/serviz.vladmin.top/manage.py", line 22, in <module>
    main()
  File "/www/wwwroot/serviz.vladmin.top/manage.py", line 13, in main
    raise ImportError(
ImportError: Couldn't import Django. Are you sure it's installed and available on your PYTHONPATH environment variable? Did you forget to activate a virtual environment?
Traceback (most recent call last):
  File "/www/wwwroot/serviz.vladmin.top/manage.py", line 11, in main
    from django.core.management import execute_from_command_line
ModuleNotFoundError: No module named 'django'

The above exception was the direct cause of the following exception:

]# pip3 freeze > req.txt

# cat req.txt
asgiref==3.4.1
distlib==0.3.8
Django==3.2.23
filelock==3.4.1
importlib-metadata==4.8.3
importlib-resources==5.4.0
platformdirs==2.4.0
pytube==12.1.2
pytz==2023.3.post1
sqlparse==0.4.4
typing_extensions==4.1.1
virtualenv==20.17.1
zipp==3.6.0

I set it up this time to use root user but to no avail. It is a very simple django admin project with literally 5 things into the database

source 44ce40ae75ae829042ad8dc069e61daf_venv/lib/python3.11/venv/scripts/common/activate
__VENV_PROMPT__[root@vladmin serviz.vladmin.top]# pip3 install pysqlite3
Collecting pysqlite3
  Using cached pysqlite3-0.5.2.tar.gz (40 kB)
  Preparing metadata (setup.py) ... done
Using legacy 'setup.py install' for pysqlite3, since package 'wheel' is not installed.
Installing collected packages: pysqlite3
    Running setup.py install for pysqlite3 ... error
    ERROR: Command errored out with exit status 1:
     command: /usr/bin/python3 -u -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-2x4jldwu/pysqlite3_2bf395c0106748f3ad0a7d3efcedc3e1/setup.py'"'"'; __file__='"'"'/tmp/pip-install-2x4jldwu/pysqlite3_2bf395c0106748f3ad0a7d3efcedc3e1/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(__file__) if os.path.exists(__file__) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-cqv6qig0/install-record.txt --single-version-externally-managed --compile --install-headers /usr/local/include/python3.6m/pysqlite3
         cwd: /tmp/pip-install-2x4jldwu/pysqlite3_2bf395c0106748f3ad0a7d3efcedc3e1/
    Complete output (20 lines):
    running install
    running build
    running build_py
    creating build
    creating build/lib.linux-x86_64-3.6
    creating build/lib.linux-x86_64-3.6/pysqlite3
    copying pysqlite3/__init__.py -> build/lib.linux-x86_64-3.6/pysqlite3
    copying pysqlite3/dbapi2.py -> build/lib.linux-x86_64-3.6/pysqlite3
    running build_ext
    Builds a C extension linking against libsqlite3 library
    building 'pysqlite3._sqlite3' extension
    creating build/temp.linux-x86_64-3.6
    creating build/temp.linux-x86_64-3.6/src
    gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -DMODULE_NAME="pysqlite3.dbapi2" -I/usr/include -I/usr/include/python3.6m -c src/module.c -o build/temp.linux-x86_64-3.6/src/module.o
    In file included from src/module.c:24:0:
    src/connection.h:27:20: fatal error: Python.h: No such file or directory
     #include "Python.h"
                        ^
    compilation terminated.
    error: command 'gcc' failed with exit status 1
    ----------------------------------------
ERROR: Command errored out with exit status 1: /usr/bin/python3 -u -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-2x4jldwu/pysqlite3_2bf395c0106748f3ad0a7d3efcedc3e1/setup.py'"'"'; __file__='"'"'/tmp/pip-install-2x4jldwu/pysqlite3_2bf395c0106748f3ad0a7d3efcedc3e1/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(__file__) if os.path.exists(__file__) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-cqv6qig0/install-record.txt --single-version-externally-managed --compile --install-headers /usr/local/include/python3.6m/pysqlite3 Check the logs for full command output.

Another hour of trying and nothing... Enjoy

itsmehemant7

Vladmin-Server I don't understand how you are doing it.
Here are steps/tips that can help you:

Install python manager
Upload your project (inside wwwroot folder)
install python version using python manager (it will take few minutes so keep calm)
Add the project in the python manager, note that you have to choose the project folder and folder that contains the wsgi.py file. in production, you don't have to use manage.py file. For example: if your project is "myproject" then you have to select project dir as "myproject" and start dir as "myproject/myproject".
Select other parameters asked, choose uwsgi or gunicorn (I prefer uwsgi), and click on "add project" (i.e. the submit button).
It will automatically create a python environment for you and start your project.
Now here is one other tip, if you are using SQLite then you have to use django 2.1 (or upgrade sqlite version in your linux OS which is a headache) or use mysql.
Create reverse proxy for the site to the port on which your project is running.

I hope it helps!!!

Vladmin-Server

itsmehemant7
Thank you! I found out that sqlite doesnt work with newer django versions so I made some tests with MySQL and it workd well but on another machine without aapanel. I will try your method and see how it goes. I guess my issue was that i was using manage.py file. Definitely so far from what i tested the uwsgi is a much better option than the rest .

Vladmin-Server

Well unfortunately it ultimately fails again and again. I followed your steps , but no matter what I try it does not work. Either I am doing something wrong but there at least should be an error. I dont see any errors at all . Just a message when creating the project "Created Failed" It creates the project and fails. THe port on which I set it up is not being used aswell which means it's definitely not running. I guess I will have to pass on using aaPanel for anything other than a wordpress and php websites. Thanks for the effort anyway . Appreciated

aaP_guisaldanha

aaPanel_Kern
Initially I used version 3.12, I tried with version 3.11.4 and it also displays failure when installing new modules.

Unfortunately I can't go back to a version before 3.11 because I use some newer python functions.

aaPanel_Kern

Is it okay to recommend that you use the command line to install?

aaP_guisaldanha

aaPanel_Kern Yes you can, please

aaP_guisaldanha

aaP_guisaldanha When I use the command systemctl restart myapp.com_pymanager the project log shows me

[2024-02-10 19:29:43 -0300] [15341] [INFO] Starting gunicorn 21.2.0
[2024-02-10 19:29:43 -0300] [15345] [INFO] Starting gunicorn 21.2.0

When I restart the project from the Python Manager interface I have the log

[2024-02-10 19:30:34 -0300] [15472] [INFO] Starting gunicorn 21.2.0
[2024-02-10 19:30:34 -0300] [15472] [INFO] Listening at: http://0.0.0.0:8000 (15472)
[2024-02-10 19:30:34 -0300] [15472] [INFO] Using worker: geventwebsocket.gunicorn.workers.GeventWebSocketWorker
[2024-02-10 19:30:34 -0300] [15475] [INFO] Booting worker with pid: 15475
[2024-02-10 19:30:34 -0300] [15477] [INFO] Starting gunicorn 21.2.0

In other words, restarting from the Python Manager interface apparently executes something more than the command systemctl restart myapp.com_pymanager

Follow the code from /etc/init.d/myapp.com_pymanager
cat /etc/init.d/myapp.com_pymanager

#!/bin/bash
# chkconfig: 2345 55 25
# description: myapp.com

### BEGIN INIT INFO
# Provides: myapp.com
# Required-Start: $all
# Required-Stop: $all
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: myapp.com
# Description: myapp.com
### END INIT INFO
/www/wwwroot/myapp.com_code//6886015edf4ab20c552c50c689a05c0e_venv/bin/gunicorn -c /www/wwwroot/myapp.com_code//gunicorn.conf project.wsgi:application

I'm using aapanel version 6.8.33
Current version: aaPanel LinuxStable 6.8.33 Release time: 2023/12/13
Python Manager 2.0

My project is running on python 3.12.0

aaP_guisaldanha

aaP_guisaldanha @aaPanel_Kern @aaPanel_Jose Still no solution?

aaP_guisaldanha

aaP_guisaldanha Still no solution? This problem persists to this day

aaPanel_Kern

Hello, I suggest you describe the problem in detail. I don’t understand what the problem is.

aaP_guisaldanha

aaPanel_Kern The problem is the following:

I use a folder inside '/www/wwwroot/a_folder' to clone a github repository
I add a new project with "Python Manager" pointing to the '/www/wwwroot/a_folder' folder for the Django Framework and use the "Install module now" option
Installation goes smoothly and no errors are displayed
Map a domain to the project
Everything works fine

The problem occurs when:

Update the github project with a new module
In the terminal, do a "git pull origin main" in the folder '/www/wwwroot/a_folder'
In the terminal, use the command '/www/wwwroot/a_folder/6886034edf6fc40c552c50c689g05c0g_venv/bin/pip install new_module'
In the aaPanel in "Python Manager" I click on "Restart Project"
The website has a problem because the "new_module" dependency that I just installed is missing, as informed in step 8

So when I install a new module, I always need to delete the project and do steps 1 to 5 again

I tried to describe step by step how the problem occurs, if it wasn't clear, please let me know so I can try to explain it another way.

aaPanel_Kern

Hello, I suggest you use the command to deploy directly?

aaP_guisaldanha

aaP_Shaun

Hello, is there an an example with ASGI, websockets and Daphne?

aaP_bofoiii229

how to set django version ?

« Previous Page