GitHub user ggrohmann edited a comment on the discussion: Question About 
Database Connections in Apache Hop Server Mode

Hey folks,

I have a question, which is related to the described matter, in particular 
running a project on a remote server. I managed to run single pipelines and 
workflows on a hop server in a docker container (long-lived). However, I 
struggle with setting up the run configuration for a workflow with linked 
pipelines and sub workflows. I followed the documentation as far as I could 
(https://hop.apache.org//manual/latest/workflow/workflow-run-configurations/native-remote-workflow-engine.html).
 

However, I receive the error, that the pipelines couldn't be resolved, when I 
run the start workflow in my local hop gui with the remote environment:
ERROR: Error starting workflow
ERROR: org.apache.hop.core.exception.HopException: 
Error serializing export interface [C:\.../start.hwf : start]
start - Unable to load pipeline 
[${PROJECT_HOME}/ingestion/get-csv-file-metadata.hpl] : can't find directory 

I tried different options, but none worked out, the last one being displayed in 
the screenshot (tried it first with both folder settings empty). 
![image](https://github.com/user-attachments/assets/698d76af-8c99-428e-8aa9-071dda817e55)
It's a rather simple workflow
![{6A7ABA90-DFA8-498D-9C28-5AB1012C936A}](https://github.com/user-attachments/assets/910ca10e-01b3-4c8b-8aa1-9dd26674c2b0)


According to the documentation, the project home (variable) should be replaced 
on the server with a local folder. That being said, I have not created the 
container with any particular environment variables or volume mounts etc. as 
this would counter the purpose of the use case.

Any suggestions what the correct configuration would look like? The workflow 
runs fine with local runtime.

Thanks

GitHub link: 
https://github.com/apache/hop/discussions/4634#discussioncomment-12821552

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to