hansva opened a new issue, #9564:
URL: https://github.com/apache/hop/issues/9564

   ### What would you like to happen?
   
   Users want to run Hop Web on their own Tomcat instead of the 
`apache/hop-web` image. The only war we build, `assemblies/web/target/hop.war` 
(about 8 MB), does not run on its own. It holds the RAP web app (static files, 
`hop-ui-rap` and the RAP/fileupload jars) but not Hop itself.
   
   The Docker build (`docker/web.Dockerfile`, `docker/unified.Dockerfile`) 
turns it into a working app by adding pieces of the client:
   
   | From the client | Into Tomcat |
   |---|---|
   | `lib/core/*` | `webapps/ROOT/WEB-INF/lib` (then removes 
`hop-ui-rcp-*.jar`, which breaks on RAP) |
   | `config/` | `webapps/ROOT/config`, with `hop-config.json` rewritten to use 
`${HOP_CONFIG_FOLDER}/projects` |
   | `plugins/` | `$CATALINA_HOME/plugins`, found through 
`HOP_PLUGIN_BASE_FOLDERS` |
   | `lib/jdbc/` | `$CATALINA_HOME/jdbc-drivers`, found through 
`HOP_SHARED_JDBC_FOLDERS` |
   | `hop-run.sh`, `hop-conf.sh`, ... | classpath rewritten with `sed` to 
`../../lib/*:WEB-INF/lib/*:lib/core/*` |
   
   Anyone deploying the war by hand has to rebuild these steps from the 
Dockerfile.
   
   ### Proposal
   
   1. Add an assembly that does those steps at build time and produces a 
self-contained war, for example `hop-web-<version>.war`: RAP web app + 
`lib/core` (without `hop-ui-rcp`) + config + plugins + JDBC drivers.
   2. Make the defaults work without environment variables: when 
`HOP_PLUGIN_BASE_FOLDERS` / `HOP_SHARED_JDBC_FOLDERS` are not set, look inside 
the deployed web app. Setting them still overrides.
   3. Have the Docker images start from this war, so the layout is defined once 
in Maven instead of in two Dockerfiles.
   4. Deploy it to Maven Central next to `hop-client`, the same way: deploy 
enabled for that module only, flattened POM with no parent and no dependencies.
   5. Document deploying to Tomcat in the user manual: the war, the 
`CATALINA_OPTS` system properties the image sets today (`HOP_CONFIG_FOLDER`, 
`HOP_AUDIT_FOLDER`, `HOP_AES_ENCODER_KEY`, ...), and the CJK font note (#8528).
   
   ### Size
   
   Roughly the client minus the SWT natives: about 380–400 MB per release, on 
top of the ~2.45 GB a release stages once `hop-client` is included (#8915). It 
stays under the ASF 850 MB package limit (`tools/check-assembly-size.sh`).
   
   ### Open questions
   
   - Should plugins live inside the war (`WEB-INF/plugins`, one file to deploy) 
or stay outside it (smaller war, plugins can be added without repackaging)? The 
image keeps them outside today.
   - Keep the thin `hop.war` as a separate artifact for people who build their 
own layout, or drop it?
   - Does the war need the command-line scripts (`hop-run.sh`, `hop-conf.sh`, 
...) at all, or are they only there for the image?
   
   ### Out of scope
   
   - Changing what goes into `lib/core`. The war takes the same set as the 
client.
   - Marketplace-optional plugins. They are not bundled, the same as in the 
client.
   
   ### Issue Priority
   
   Priority: 2
   
   ### Issue Component
   
   Component: Hop Web


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to