Deploying LuxCoreRender: Difference between revisions
Jump to navigation
Jump to search
| Line 17: | Line 17: | ||
Please note we deliberately exclude the dependencies (aka LuxCoreDeps) from the deployment scope. Indeed: | Please note we deliberately exclude the dependencies (aka <code>LuxCoreDeps</code>) from the deployment scope. Indeed: | ||
* Dependencies are not intended for end-users, so deployment is not applicable. | * 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. | * Up-to-date dependencies are necessary for LuxCore development and tests, so they should have been released for a while when LuxCore deployment occurs. | ||
Revision as of 15:22, 19 April 2026
Releasing and Deploying LuxCoreRender
Audience, Scope and Prerequisites
This document is intended for LuxCoreRender administrators only.
Releasing refers to the process of finalizing a version of LuxCore, i.e. defining a state of LuxCore which can be made available to end-users.
Deployment refers to the process of making a new release of LuxCoreRender available to users.
The scope of Deployment is restricted to the following components:
- LuxCore Python Wheels (aka
pyluxcore) - LuxCore Samples (aka
luxcoreuiandluxcoreconsole) - BlendLuxCore
Please note we deliberately exclude the dependencies (aka 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 targeted LuxCore components are buildable and reasonably tested.
Buildability: the component must by buildable by Continuous Integration. This can be checked by the following Github Actions:
- Wheels:
Luxcore Python Wheel Builder