From 9eff0de2679f3280fe0da7da24b56199232ca5d1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ra=C3=BAl=20Barroso?= Date: Tue, 2 Apr 2024 13:23:26 +0200 Subject: [PATCH] doc: include more examples Uses https://github.com/ConduitIO/conduit/pull/1447 --- docs/pipeline-configuration-files/getting-started.mdx | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/docs/pipeline-configuration-files/getting-started.mdx b/docs/pipeline-configuration-files/getting-started.mdx index 62f57b85..05808565 100644 --- a/docs/pipeline-configuration-files/getting-started.mdx +++ b/docs/pipeline-configuration-files/getting-started.mdx @@ -9,7 +9,15 @@ provisioned by Conduit at startup. It's as simple as creating a YAML file that defines pipelines, connectors, processors, and their corresponding configurations. -## Example pipeline (file to file) +## Example pipeline + +:::tip + +In our [Conduit repository](https://github.com/ConduitIO/conduit), you can find [more examples](https://github.com/ConduitIO/conduit/tree/main/examples/pipelines), but to ilustrate a simple use case we'll show a pipeline using a file as a Source, and another file as a Destination. + +::: + + Create a folder called `pipelines` at the same level as your Conduit binary. Inside of that folder create a file named `file-to-file.yml`.