jumpserver/apps/common
ibuler 36813f64db perf: 修改 device platform 支持 su 2023-04-11 19:32:29 +08:00
..
api perf: 优化导入导出 2023-03-10 19:23:49 +08:00
auth
const
db
drf perf: 优化 warning 2023-03-20 09:59:34 +08:00
hashers
management
migrations
plugins
sdk feat: 支持飞书国际版(lark) 2023-03-10 15:13:12 +08:00
serializers perf: 修改 device platform 支持 su 2023-04-11 19:32:29 +08:00
templatetags
urls
utils fix: 修复日志记录到syslog时中文编码问题 2023-03-15 19:46:01 +08:00
views perf: 优化账号活动日志界面的提示及操作日志的字段内容 2023-03-27 18:23:55 +08:00
README.md
__init__.py
apps.py
cache.py
decorators.py
exceptions.py
local.py
permissions.py
signal_handlers.py
signals.py
struct.py
tasks.py
tests.py
thread_pools.py
tree.py
validators.py fix: 手机号码校验逻辑问题 2023-04-10 18:00:39 +08:00

README.md

Common app

Common app provide common view, function or others.

Common app shouldn't rely on other apps, because It may lead to cycle import.

If your want to implement some function or class, you should think whether other app use or not. If yes, You should make in common.

If the ability more relate to your app tightness, It's mean your app provide this ability, not common, You should write it on your app utils.

Celery usage

JumpServer use celery to run task async. Using redis as the broker, so you should run a redis instance

Run redis

$ yum -y install redis 

or

$ docker run -name jumpserver-redis -d -p 6379:6379 redis redis-server

Write tasks in app_name/tasks.py

ops/tasks.py

from __future__ import absolute_import

import time
from celery import shared_task
from common import celery_app


@shared_task
def longtime_add(x, y):
    print 'long time task begins'
    # sleep 5 seconds
    time.sleep(5)
    print 'long time task finished'
    return x + y
    

@celery_app.task(name='hello-world')
def hello():
    print 'hello world!'
  

Run celery in development

$ cd apps
$ celery -A common worker -l info 

Test using task

$ ./manage.py shell
>>> from ops.tasks import longtime_add
>>> res = longtime_add.delay(1, 2)
>>> res.get()