You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hop.apache.org by "mzxc (via GitHub)" <gi...@apache.org> on 2023/07/07 08:36:23 UTC

[I] [Feature Request]: Why isn't there a detailed deployment manual (hop)

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

   ### What would you like to happen?
   
   After the development of hop project, how to deploy to hop server without detailed instructions, which is very confusing for novices, how to package the project, how to package the project should be published, published to where, how to use with hop server, these documents should have a detailed explanation, the official website completely no relevant documents, too difficult to use
   
   ### Issue Priority
   
   Priority: 1
   
   ### Issue Component
   
   Component: Hop Server


-- 
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: issues-unsubscribe@hop.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Feature Request]: Why isn't there a detailed deployment manual (hop)

Posted by "hansva (via GitHub)" <gi...@apache.org>.
hansva commented on issue #3062:
URL: https://github.com/apache/hop/issues/3062#issuecomment-1625137494

   I do agree the docs can always be improved and moving things from development to production isn't really documented.
   Though we do have documentation on how to run a project with our docker image and how to use airflow to schedule things.
   
   That being said Hop isn't a client/server architecture. 
   The Hop server is an extension to run pipelines/workflows on a remote location. for example you only have access to a certain database when executing a pipeline on a server in your datacenter. Or you need more memory than your local environment provides. 
   
   It has no features to do scheduling/reporting/logging.
   
   so moving to production can be as simple as copy pasting your workflows to a server registering a project with hop-conf and executing something with hop-run


-- 
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: issues-unsubscribe@hop.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org