Advanced: New Deploying Blender page #104811

Merged
Brecht Van Lommel merged 2 commits from brecht/blender-manual:deploying into blender-v4.2-release 2024-06-07 14:49:37 +02:00
Showing only changes of commit 11dcba5391 - Show all commits

View File

@ -1,8 +1,8 @@
.. _deploying-blender:
*****************
Deploying Blender
*****************
*******************************
Deploying Blender in Production
*******************************
It is possible to deploy Blender in environments that are more
restricted, use automation or have other special requirements.
@ -20,8 +20,8 @@ standard file management tools.
New Blender versions may add, remove or changes functionality that
change the results of production files. For a given project, it is
advisable to use a single LTS (long term support) version of Blender.
LTS versions receive bug fixes for two years.
advisable to use a single :abbr:`LTS (Long-Term-Support)` version
of Blender. LTS versions receive bug fixes for two years.
Working Offline
===============
@ -32,7 +32,8 @@ By default Blender does not access the internet, however this can be
enabled in the System preferences with the Online Access option.
Working offline can be enforced by running with the ``--offline-mode``
:ref:`command line argument <command-line-args-network-options>`.
:ref:`command line argument <command-line-args-network-options>`. Users
will then be unable to enable online access in the preferences.
Bundling Extensions
===================
@ -45,12 +46,15 @@ or in a system directory.
The location of this system extension repository can be manually configured
in the Extensions preferences.
The ``$BLENDER_SYSTEM_REPOSITORY``
The ``$BLENDER_SYSTEM_EXTENSIONS``
:ref:`environment variable <command-line-args-environment-variables>`
can also set the default location. This is a directory, within which a
``system`` directory should exist. Each extension zip file should be
extracted to its own folder, and which should then contain a
``blender_manifest.toml`` file.
``system`` directory should exist. Then extract extension packages there,
with a resulting path like this:
.. code-block:: bash
$BLENDER_SYSTEM_EXTENSIONS/system/my-addon/blender_manifest.toml
Bundling Scripts
================
@ -72,8 +76,11 @@ Startup Scripts
The Blender Python API can be used to customize Blender. This includes
changing preferences, changing the startup file and adding UI elements.
For example a ``startup/enable_addons.py`` script can be created to
enable a set of add-ons for every user.
For example, a script can enable add-ons for every user.
.. code-block:: bash
$BLENDER_SYSTEM_SCRIPTS/startup/enable_addons.py
.. code-block:: python