tutor/docs/tutorials/index.rst

Tutorials
=========

Open edX customization
----------------------

.. toctree::
   :maxdepth: 1

   plugin
   theming
   edx-platform-settings
   google-smtp
   nightly

System administration
---------------------

.. toctree::
   :maxdepth: 1

   scale
   portainer
   podman
   proxy
   datamigration
   multiplatforms
   oldreleases
   arm64

.. Note: maybe we should create a dedicated tutorial category in the Open edX forum?
.. Other tutorials can be found in the official Tutor forums, `in the "Tutorials" category <https://discuss.overhang.io/c/tutor/tutorials/13>`__.
feat: migrate to plugins.v1 with filters & actions This is a very large refactoring which aims at making Tutor both more extendable and more generic. Historically, the Tutor plugin system was designed as an ad-hoc solution to allow developers to modify their own Open edX platforms without having to fork Tutor. The plugin API was simple, but limited, because of its ad-hoc nature. As a consequence, there were many things that plugin developers could not do, such as extending different parts of the CLI or adding custom template filters. Here, we refactor the whole codebase to make use of a generic plugin system. This system was inspired by the Wordpress plugin API and the Open edX "hooks and filters" API. The various components are added to a small core thanks to a set of actions and filters. Actions are callback functions that can be triggered at different points of the application lifecycle. Filters are functions that modify some data. Both actions and filters are collectively named as "hooks". Hooks can optionally be created within a certain context, which makes it easier to keep track of which application created which callback. This new hooks system allows us to provide a Python API that developers can use to extend their applications. The API reference is added to the documentation, along with a new plugin development tutorial. The plugin v0 API remains supported for backward compatibility of existing plugins. Done: - Do not load commands from plugins which are not enabled. - Load enabled plugins once on start. - Implement contexts for actions and filters, which allow us to keep track of the source of every hook. - Migrate patches - Migrate commands - Migrate plugin detection - Migrate templates_root - Migrate config - Migrate template environment globals and filters - Migrate hooks to tasks - Generate hook documentation - Generate patch reference documentation - Add the concept of action priority Close #499. 2022-02-07 18:11:43 +01:00			`Tutorials`
			`=========`

			`Open edX customization`
			`----------------------`

			`.. toctree::`
			`:maxdepth: 1`

			`plugin`
			`theming`
			`edx-platform-settings`
			`google-smtp`
			`nightly`

			`System administration`
			`---------------------`

			`.. toctree::`
			`:maxdepth: 1`

			`scale`
			`portainer`
			`podman`
			`proxy`
			`datamigration`
			`multiplatforms`
			`oldreleases`
			`arm64`

docs: move forum to discuss.openedx.org Now that Tutor is the official community installation for Open edX, it no longer makes sense to host a forum that is separate from the general Open edX forum. Moving conversations there will encourage cross-communication between projects and maintainers. This change is part of a larger overhaul described in this Tutor enhancement proposal (TEP): https://discuss.overhang.io/t/tep-rethinking-the-tutor-maintainers-program/2724 In the future, plugin maintainers should point their users to the Open edX forum as well. They are encouraged to create dedicated "tutor-pluginnname" tags on the forum and to set their notification level to "watching". 2022-05-19 10:25:28 +02:00			`.. Note: maybe we should create a dedicated tutorial category in the Open edX forum?`
			.. Other tutorials can be found in the official Tutor forums, `in the "Tutorials" category <https://discuss.overhang.io/c/tutor/tutorials/13>`__.