Deploying LuxCoreRender: Difference between revisions
| Line 6: | Line 6: | ||
The term <b>Releasing</b> refers to the process of finalizing a version of LuxCore, ie defining a state of LuxCore which can be made available to end-users. | The term <b>Releasing</b> refers to the process of finalizing a version of LuxCore, ie defining a state of LuxCore which can be made available to end-users. | ||
The term <b>Deployment</b> refers to the process of making a new release of LuxCoreRender available to users. | The term <b>Deployment</b> refers to the process of making a new release of LuxCoreRender available to users. | ||
Revision as of 15:05, 19 April 2026
Releasing and Deploying LuxCoreRender
Audience, Objectives, Scope and Prerequisites
This document is intended for LuxCoreRender administrators only.
The term Releasing refers to the process of finalizing a version of LuxCore, ie defining a state of LuxCore which can be made available to end-users.
The term Deployment refers to the process of making a new release of LuxCoreRender available to users.
The scope of Deployment is restricted to: - LuxCore, encompassing the Python wheels (aka `pyluxcore`) and the Samples (aka `luxcoreui` and `luxcoreconsole`) - BlendLuxCore
Please note we deliberately exclude the dependencies (LuxCoreDeps) from the deployment scope. Indeed: - Dependencies are not intended for end-users, so deployment is not applicable. - Up-to-date dependencies are necessary for LuxCore development and tests, so they should have been released for a while when LuxCore deployment occurs.
Prerequisites
We assume that the LuxCore elements are buildable and have been reasonably tested.