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

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_mrpk8882

aaP_guisaldanha

I hope you are doing well friend I am facing a problem I am troubled for a long time I am not able to make my project live can you help me this is my whatsapp number if you are comfortable then you can send it to me on whatsapp I will be grateful to you (+918178544747)

I have uploaded a video of this problem on YouTube. You can watch this video now.
https://www.youtube.com/watch?v=g9zxiukkk-k

aaP_Shaun

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

aaP_bofoiii229

how to set django version ?

aaP_gabe.cam132

I'm having a problem, when I try to create the project it always fails to start up, this is because the virtual environment created comes without gunicorn, even though I've already installed it and the other project requirements previously

aaPanel_Kern

Hello, is there an error in the installation process? Can the server be connected to the PYPI server?

aaP_gabe.cam132

aaP_demo1

Hello,

I have an issue with jieba library when executing makemigrations command

__VENV_PROMPT__[root@localhost DjangoBlog]# /www/wwwroot/default/DjangoBlog/8658305af42d6efded53c296d677d3ba_venv/bin/python3.12 manage.py makemigrations

Results

Traceback (most recent call last):
  File "/www/wwwroot/default/DjangoBlog/manage.py", line 22, in <module>
    execute_from_command_line(sys.argv)
  File "/www/wwwroot/default/DjangoBlog/8658305af42d6efded53c296d677d3ba_venv/lib/python3.12/site-packages/django/core/management/__init__.py", line 442, in execute_from_command_line
    utility.execute()
  File "/www/wwwroot/default/DjangoBlog/8658305af42d6efded53c296d677d3ba_venv/lib/python3.12/site-packages/django/core/management/__init__.py", line 436, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/www/wwwroot/default/DjangoBlog/8658305af42d6efded53c296d677d3ba_venv/lib/python3.12/site-packages/django/core/management/base.py", line 412, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/www/wwwroot/default/DjangoBlog/8658305af42d6efded53c296d677d3ba_venv/lib/python3.12/site-packages/django/core/management/base.py", line 453, in execute
    self.check()
  File "/www/wwwroot/default/DjangoBlog/8658305af42d6efded53c296d677d3ba_venv/lib/python3.12/site-packages/django/core/management/base.py", line 485, in check
    all_issues = checks.run_checks(
                 ^^^^^^^^^^^^^^^^^^
  File "/www/wwwroot/default/DjangoBlog/8658305af42d6efded53c296d677d3ba_venv/lib/python3.12/site-packages/django/core/checks/registry.py", line 88, in run_checks
    new_errors = check(app_configs=app_configs, databases=databases)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/www/wwwroot/default/DjangoBlog/8658305af42d6efded53c296d677d3ba_venv/lib/python3.12/site-packages/django/core/checks/urls.py", line 42, in check_url_namespaces_unique
    all_namespaces = _load_all_namespaces(resolver)
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/www/wwwroot/default/DjangoBlog/8658305af42d6efded53c296d677d3ba_venv/lib/python3.12/site-packages/django/core/checks/urls.py", line 61, in _load_all_namespaces
    url_patterns = getattr(resolver, "url_patterns", [])
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/www/wwwroot/default/DjangoBlog/8658305af42d6efded53c296d677d3ba_venv/lib/python3.12/site-packages/django/utils/functional.py", line 57, in __get__
    res = instance.__dict__[self.name] = self.func(instance)
                                         ^^^^^^^^^^^^^^^^^^^
  File "/www/wwwroot/default/DjangoBlog/8658305af42d6efded53c296d677d3ba_venv/lib/python3.12/site-packages/django/urls/resolvers.py", line 715, in url_patterns
    patterns = getattr(self.urlconf_module, "urlpatterns", self.urlconf_module)
                       ^^^^^^^^^^^^^^^^^^^
  File "/www/wwwroot/default/DjangoBlog/8658305af42d6efded53c296d677d3ba_venv/lib/python3.12/site-packages/django/utils/functional.py", line 57, in __get__
    res = instance.__dict__[self.name] = self.func(instance)
                                         ^^^^^^^^^^^^^^^^^^^
  File "/www/wwwroot/default/DjangoBlog/8658305af42d6efded53c296d677d3ba_venv/lib/python3.12/site-packages/django/urls/resolvers.py", line 708, in urlconf_module
    return import_module(self.urlconf_name)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/www/wwwroot/default/DjangoBlog/8658305af42d6efded53c296d677d3ba_venv/lib/python3.12/importlib/__init__.py", line 90, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1381, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1354, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1325, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 929, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 994, in exec_module
  File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
  File "/www/wwwroot/default/DjangoBlog/djangoblog/urls.py", line 22, in <module>
    from haystack.views import search_view_factory
  File "/www/wwwroot/default/DjangoBlog/8658305af42d6efded53c296d677d3ba_venv/lib/python3.12/site-packages/haystack/views.py", line 12, in <module>
    class SearchView:
  File "/www/wwwroot/default/DjangoBlog/8658305af42d6efded53c296d677d3ba_venv/lib/python3.12/site-packages/haystack/views.py", line 16, in SearchView
    results = EmptySearchQuerySet()
              ^^^^^^^^^^^^^^^^^^^^^
  File "/www/wwwroot/default/DjangoBlog/8658305af42d6efded53c296d677d3ba_venv/lib/python3.12/site-packages/haystack/query.py", line 25, in __init__
    self._determine_backend()
  File "/www/wwwroot/default/DjangoBlog/8658305af42d6efded53c296d677d3ba_venv/lib/python3.12/site-packages/haystack/query.py", line 58, in _determine_backend
    self.query = connections[backend_alias].get_query()
                 ~~~~~~~~~~~^^^^^^^^^^^^^^^
  File "/www/wwwroot/default/DjangoBlog/8658305af42d6efded53c296d677d3ba_venv/lib/python3.12/site-packages/haystack/utils/loading.py", line 114, in __getitem__
    self.thread_local.connections[key] = load_backend(
                                         ^^^^^^^^^^^^^
  File "/www/wwwroot/default/DjangoBlog/8658305af42d6efded53c296d677d3ba_venv/lib/python3.12/site-packages/haystack/utils/loading.py", line 60, in load_backend
    return import_class(full_backend_path)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/www/wwwroot/default/DjangoBlog/8658305af42d6efded53c296d677d3ba_venv/lib/python3.12/site-packages/haystack/utils/loading.py", line 22, in import_class
    module_itself = importlib.import_module(module_path)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/www/wwwroot/default/DjangoBlog/8658305af42d6efded53c296d677d3ba_venv/lib/python3.12/importlib/__init__.py", line 90, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/www/wwwroot/default/DjangoBlog/djangoblog/whoosh_cn_backend.py", line 25, in <module>
    from jieba.analyse import ChineseAnalyzer
ImportError: cannot import name 'ChineseAnalyzer' from 'jieba.analyse' (/www/wwwroot/default/DjangoBlog/8658305af42d6efded53c296d677d3ba_venv/lib/python3.12/site-packages/jieba/analyse/__init__.py)

library files and source code checked out fine:

please advise

aaPanel_Kern

Hello, it is recommended that you lower the python version and re-deploy it normally?

aaP_demo1

aaPanel_Kern
Redeploy fix the problem. However, it can't start from python manager app. No error log shown. Please help what should I do?

aaPanel_Kern

Hello, is it normal to use the command line to start manually with the official tutorial?

aaP_demo1

aaPanel_Kern
Yes, When I executed the command line manually it is working.

root@mail:/www/wwwroot/default/DjangoBlog# /www/wwwroot/default/DjangoBlog/ef0f93c83e374876a61da0d4d16f36ab_venv/bin/python3.12 manage.py runserver
Watching for file changes with StatReloader
[2025-03-20 10:29:52,024] INFO [django.utils.autoreload.run_with_reloader:668 autoreload] Watching for file changes with StatReloader
Performing system checks...

System check identified no issues (0 silenced).
March 20, 2025 - 10:29:53
Django version 4.2.20, using settings 'djangoblog.settings'
Starting development server at http://127.0.0.1:8000/
Quit the server with CONTROL-C.

Here's the error logs:

[2025-03-20 09:30:58 +0700] [256286] [INFO] Starting gunicorn 23.0.0
[2025-03-20 09:30:58 +0700] [256286] [INFO] Listening at: http://0.0.0.0:8000 (256286)
[2025-03-20 09:30:58 +0700] [256286] [INFO] Using worker: gthread
[2025-03-20 09:30:58 +0700] [256287] [INFO] Booting worker with pid: 256287
[2025-03-20 09:30:58 +0700] [256287] [ERROR] Exception in worker process
Traceback (most recent call last):
  File "/www/server/python_manager/versions/3.12.0/lib/python3.12/site-packages/gunicorn/arbiter.py", line 608, in spawn_worker
    worker.init_process()
  File "/www/server/python_manager/versions/3.12.0/lib/python3.12/site-packages/gunicorn/workers/gthread.py", line 94, in init_process
    super().init_process()
  File "/www/server/python_manager/versions/3.12.0/lib/python3.12/site-packages/gunicorn/workers/base.py", line 135, in init_process
    self.load_wsgi()
  File "/www/server/python_manager/versions/3.12.0/lib/python3.12/site-packages/gunicorn/workers/base.py", line 147, in load_wsgi
    self.wsgi = self.app.wsgi()
                ^^^^^^^^^^^^^^^
  File "/www/server/python_manager/versions/3.12.0/lib/python3.12/site-packages/gunicorn/app/base.py", line 66, in wsgi
    self.callable = self.load()
                    ^^^^^^^^^^^
  File "/www/server/python_manager/versions/3.12.0/lib/python3.12/site-packages/gunicorn/app/wsgiapp.py", line 57, in load
    return self.load_wsgiapp()
           ^^^^^^^^^^^^^^^^^^^
  File "/www/server/python_manager/versions/3.12.0/lib/python3.12/site-packages/gunicorn/app/wsgiapp.py", line 47, in load_wsgiapp
    return util.import_app(self.app_uri)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/www/server/python_manager/versions/3.12.0/lib/python3.12/site-packages/gunicorn/util.py", line 370, in import_app
    mod = importlib.import_module(module)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/www/server/python_manager/versions/3.12.0/lib/python3.12/importlib/__init__.py", line 90, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1381, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1354, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1318, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'djangob'
[2025-03-20 09:30:58 +0700] [256287] [INFO] Worker exiting (pid: 256287)
[2025-03-20 09:30:58 +0700] [256286] [ERROR] Worker (pid:256287) exited with code 3
[2025-03-20 09:30:58 +0700] [256286] [ERROR] Shutting down: Master
[2025-03-20 09:30:58 +0700] [256286] [ERROR] Reason: Worker failed to boot.

« Previous Page