hanghangliu commented on a change in pull request #3154:
URL: https://github.com/apache/incubator-gobblin/pull/3154#discussion_r535878064



##########
File path: gobblin-docs/user-guide/Docker-Integration.md
##########
@@ -18,68 +18,68 @@ The `gobblin/gobblin-wikipedia` repository contains images 
that run the Gobblin
 
 The `gobblin/gobblin-standalone` repository contains images that run a 
[Gobblin standalone service](Gobblin-Deployment#standalone-architecture) inside 
a Docker container. These images provide an easy and simple way to setup a 
Gobblin standalone service on any Docker compatible machine.
 
+The `gobblin/gobblin-service` repository contains images that run [Gobblin as 
a 
service](Building-Gobblin-as-a-Service#running-gobblin-as-a-service-with-docker),
 which is a service that takes in a user request (a logical flow) and converts 
it into a series of Gobblin Jobs, and monitors these jobs in a distributed 
manner.
+
 The `gobblin/gobblin-base` and `gobblin/gobblin-distributions` repositories 
are for internal use only, and are primarily useful for Gobblin developers.
 
-## Gobblin-Wikipedia Repository
+# Run Gobblin Standalone
+
+The Docker images for this repository can be found on Docker Hub 
[here](https://hub.docker.com/r/gobblin/gobblin-standalone/). These images run 
a Gobblin standalone service inside a Docker container. The Gobblin standalone 
service is a long running process that can run Gobblin jobs defined in a `.job` 
or `.pull` file. The job / pull files are submitted to the standalone service 
by placing them in a directory on the local filesystem. The standalone service 
monitors this directory for any new job / pull files and runs them either 
immediately or on a scheduled basis (more information on how this works can be 
found 
[here](Working-with-Job-Configuration-Files#adding-or-changing-job-configuration-files)).
 Running the Gobblin standalone service inside a Docker container allows 
Gobblin to pick up job / pull files from a directory on the host filesystem, 
run the job, and write the output back the host filesystem. All the heavy 
lifting is done inside a Docker container, the user just needs to
  worry about defining and submitting job / pull files. The goal is to provide 
a easy to setup environment for the Gobblin standalone service.

Review comment:
       Added a GaaS section with instruction of starting the service. Will add 
a detailed end-to-end flow example in the future for GaaS on docker.




----------------------------------------------------------------
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.

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


Reply via email to