mirror of https://github.com/jumpserver/jumpserver
![]() * [Update] 拆分user permission * [Update] 修改 ops command * [Update] 修改setting无法生效的问题 * [Update] 修复授权详情-授权资产或节点添加资产失败 * [Bugfix] 修复组织管理员运行命令时的问题 * [Update] 修复命令执行左侧树点击问题 |
||
---|---|---|
.. | ||
auth | ||
fields | ||
migrations | ||
mixins | ||
parsers | ||
renders | ||
templatetags | ||
urls | ||
utils | ||
README.md | ||
__init__.py | ||
api.py | ||
apps.py | ||
compat.py | ||
const.py | ||
decorator.py | ||
drfmetadata.py | ||
exceptions.py | ||
filters.py | ||
http.py | ||
local.py | ||
permissions.py | ||
serializers.py | ||
signals.py | ||
signals_handlers.py | ||
struct.py | ||
tasks.py | ||
tests.py | ||
tree.py | ||
validators.py |
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()