2014-05-31 13:25:39 +02:00
|
|
|
.. index:: installation
|
|
|
|
|
|
|
|
=======
|
2014-05-29 23:57:19 +02:00
|
|
|
Install
|
|
|
|
=======
|
|
|
|
|
2014-05-31 13:25:39 +02:00
|
|
|
Working Environment
|
|
|
|
===================
|
|
|
|
|
2020-03-03 15:04:34 +01:00
|
|
|
To get a running work environment use `pipenv`_.
|
2014-05-31 13:25:39 +02:00
|
|
|
|
2020-03-03 15:04:34 +01:00
|
|
|
.. _pipenv: https://pipenv.kennethreitz.org/en/latest/
|
2014-05-31 13:25:39 +02:00
|
|
|
|
2020-03-03 15:04:34 +01:00
|
|
|
To get started install `pip` and `pipenv` and use `pipenv install --dev`:
|
2014-05-31 13:25:39 +02:00
|
|
|
|
|
|
|
.. code-block:: sh
|
|
|
|
|
2020-03-03 15:04:34 +01:00
|
|
|
$ apt install python3-pip
|
|
|
|
$ python3 -m pip install --user -U pipenv
|
|
|
|
$ pipenv install --dev
|
2014-05-31 13:25:39 +02:00
|
|
|
|
|
|
|
.. index:: celery, worker, ldap queue
|
2014-05-31 13:26:48 +02:00
|
|
|
|
|
|
|
Running the Celery worker
|
|
|
|
=========================
|
|
|
|
|
|
|
|
gvaldap uses the `Celery`_ distributed task queue system. The gvaldap logix is
|
|
|
|
executed by a celery worker. After all dependencies are installed you can go
|
|
|
|
into the gvaldap directory and run the celery worker with:
|
|
|
|
|
|
|
|
.. code-block:: sh
|
|
|
|
|
|
|
|
$ cd gvaldap
|
2020-03-03 15:04:34 +01:00
|
|
|
$ pipenv run celery -A ldaptasks worker -Q web -l info
|
2014-05-31 13:26:48 +02:00
|
|
|
|
|
|
|
.. _Celery: http://www.celeryproject.org/
|