Add optional Python/JEP support to simple Docker image#723
Open
moqui-industrial wants to merge 1 commit into
Open
Add optional Python/JEP support to simple Docker image#723moqui-industrial wants to merge 1 commit into
moqui-industrial wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds optional Python and JEP (Java Embedded Python) support to the simple Docker image build. The build is completely opt-in and auto-detected, introducing zero modifications to the core framework's
build.gradle.All opinionated Swarm/stack deployment configurations from the previous PR attempt have been removed, as they will be moved to a separate
moqui-deploycomponent.Changes
WITH_JEPbuild argument (defaultfalse). Whentrue, it installs Python 3 dependencies, creates a virtual environment inside the runtime directory, and pre-installsnumpyandjep.moqui-jepcomponent is present underruntime/component/. If detected, it automatically passes--build-arg WITH_JEP=trueto the build command.libjep.so) inside the virtualenv and starts the JVM with the required-Djep.liband-Djep_site_pkgssystem properties.This keeps all JEP configurations completely isolated inside the
moqui-jepcomponent and ensures the Docker build remains clean and standard when JEP is not in use.