6
0
mirror of https://github.com/ChristianLight/tutor.git synced 2025-01-09 16:36:29 +00:00

chore: fixed typos (#1137)

This commit is contained in:
Emad Rad 2024-10-14 20:08:21 +03:30 committed by GitHub
parent 2d0600cc2c
commit d0187e9cc9
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
4 changed files with 4 additions and 4 deletions

View File

@ -387,7 +387,7 @@ If you don't create your fork from this tag, you *will* have important compatibi
Getting and customizing Translations
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Tutor builds images with the latest translations using the ``atlas pull`` `command <https://github.com/openedx/openedx-atlas>`__.
Tutor builds images with the latest translations using the ``atlas pull`` `command <https://github.com/openedx/openedx-atlas>`_.
By default the translations are pulled from the `openedx-translations repository <https://github.com/openedx/openedx-translations>`_
from the ``ATLAS_REVISION`` branch. You can use custom translations on your fork of the openedx-translations repository by setting the following configuration parameters:

View File

@ -99,7 +99,7 @@ To open a python shell in the LMS or CMS, run::
You can then import edx-platform and django modules and execute python code.
To rebuild assets, you can run the ``build-dev`` NPM script that comes with edx-plaform::
To rebuild assets, you can run the ``build-dev`` NPM script that comes with edx-platform::
tutor dev run lms npm run build-dev

View File

@ -152,7 +152,7 @@ Plugins can customize any Kubernetes resource in Tutor by overriding the definit
::
# myplugin/tutormyplugin/patches/k8s-override
apiVersion: v1
kind: PersistentVolumeClaim
metadata:

View File

@ -176,7 +176,7 @@ To learn more, check out `this GitHub issue <https://github.com/overhangio/tutor
High resource consumption by Docker on ``tutor images build``
-------------------------------------------------------------
Some Docker images include many independent layers which are built in parallel by BuildKit. As a consequence, building these images will use up a lot of resources, sometimes even crashing the Docker daemon. To bypass this issue, we should explicitely limit the `maximum parallelism of BuildKit <https://docs.docker.com/build/buildkit/configure/#max-parallelism>`__. Create a ``buildkit.toml`` configuration file with the following contents::
Some Docker images include many independent layers which are built in parallel by BuildKit. As a consequence, building these images will use up a lot of resources, sometimes even crashing the Docker daemon. To bypass this issue, we should explicitly limit the `maximum parallelism of BuildKit <https://docs.docker.com/build/buildkit/configure/#max-parallelism>`__. Create a ``buildkit.toml`` configuration file with the following contents::
[worker.oci]
max-parallelism = 2