Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
A
AlekSIS-Core
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Terraform modules
Monitor
Service Desk
Analyze
Contributor analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
AlekSIS®
Official
AlekSIS-Core
Commits
ceee8caa
Verified
Commit
ceee8caa
authored
3 years ago
by
Nik | Klampfradler
Browse files
Options
Downloads
Patches
Plain Diff
[Docs] Document periodic tasks
parent
8a530643
No related branches found
Branches containing commit
No related tags found
Tags containing commit
1 merge request
!910
[Docs] Further improvements
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
docs/admin/02_install.rst
+2
-0
2 additions, 0 deletions
docs/admin/02_install.rst
docs/admin/07_tasks.rst
+26
-0
26 additions, 0 deletions
docs/admin/07_tasks.rst
with
28 additions
and
0 deletions
docs/admin/02_install.rst
+
2
−
0
View file @
ceee8caa
...
...
@@ -125,6 +125,8 @@ from `yarnpkg`, collect static files, and migrate the database to the final sche
aleksis-admin migrate
aleksis-admin createinitialrevisions
.. _core-configure-uwsgi:
Configure uWSGI
~~~~~~~~~~~~~~~
...
...
This diff is collapsed.
Click to expand it.
docs/admin/07_tasks.rst
0 → 100644
+
26
−
0
View file @
ceee8caa
Background tasks
================
Operations that are expected to take a long time are run as background tasks.
For this, at least one `Celery`_ worker has to be running, e.g. by coupling it
with uWSGI as laid out in :ref:`core-configure-uwsgi`.
If a task is triggered from the AlekSIS frontend, for example by starting an import
job, a progress page is displayed, and the result of the job is waited for.
.. _core-periodic-tasks:
Periodic tasks
~~~~~~~~~~~~~~
Some tasks are also run on a schedule. For example, the backup job is run on
a regular basis.
All tasks in AlekSIS that are expected to run have a default schedule, which
is registered when migrating the database. Changing this default schedule
is currently only possible through the Django Admin backend, under
*Admin → Backend Admin*.
Under the *Periodic Tasks* app, you can define schedules and tasks. The names
of tasks you can add manually are documented in the respective sections
of the manual.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment