Files
jumpserver/apps/common
fit2bot 2fcbfe9f21 perf: 优化 tree nodes 避免太慢 (#12472)
* perf: 优化 tree nodes 避免太慢

perf: 优化大量资产上的资产数生成比较慢

perf: 优化节点树

perf: 修改 tree nooooooooodes

perf: 优化一些 api 比较大的问题

perf: 优化平台 api

perf: 分页返回同步树

perf: 优化节点树

perf: 深度优化节点树

* perf: remove unused config

---------

Co-authored-by: ibuler <ibuler@qq.com>
2024-01-02 16:11:56 +08:00
..
2023-10-31 02:43:33 -05:00
2023-10-17 11:19:13 +08:00
2023-11-08 19:05:51 +08:00
2023-12-20 10:57:58 +05:00
2022-10-14 19:40:51 +08:00
2023-09-13 17:43:29 +08:00
2022-03-07 19:02:37 +08:00
2023-12-21 16:51:36 +08:00
2023-11-14 19:21:33 +08:00
2023-03-09 18:12:56 +08:00
2023-07-24 14:09:22 +08:00
2023-10-13 14:40:40 +08:00
2023-03-09 13:02:34 +08:00
2022-02-17 20:13:31 +08:00
2023-07-24 11:52:25 +08:00

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()