Skip to content

spelling and links #61

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 8, 2022
Merged

spelling and links #61

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions blog/2022-01-31-dynamic-workflows.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,9 +5,9 @@ authors: doug
tags: [Netflix Conductor, Orkes, Conductor, orchestration, image processing, fork, dynamic fork, tutorial, 2022]
---

In recent posts, we have built several image processing workflows with Conductor. In our first post, we created an [image processing workflow for one image](image-processing-workflow-with-conductor) - where we provide an image along with the desired output dimensions and format. The workflow output a link on Amazon S3 to the desired file.
In recent posts, we have built several image processing workflows with Conductor. In our first post, we created an [image processing workflow for one image](/content/blog/image-processing-workflow-with-conductor) - where we provide an image along with the desired output dimensions and format. The workflow output a link on Amazon S3 to the desired file.

In the 2nd example, we used the FORK System task to create [multiple images](image-processing-multiple-images-forks) in parallel. The number of images was hardcoded in the workflow - as FORK generates exactly as many paths as are coded into the workflow.
In the 2nd example, we used the FORK System task to create [multiple images](/content/blog/image-processing-multiple-images-forks) in parallel. The number of images was hardcoded in the workflow - as FORK generates exactly as many paths as are coded into the workflow.

As number of images is hardcoded in the workflow - only 2 images are created. When it comes to image generation, there is often a need for more images (as new formats become popular) or sizes - as more screens are supported.

Expand Down
4 changes: 2 additions & 2 deletions blog/2022-01-31-image-processing-fork.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ tags: [Netflix Conductor, Orkes, Conductor, orchestration, image processing, for
---


In our [previous post](image-processing-workflow-with-conductor) on image processing workflows, we built a Netflix Conductor workflow that took an image input, and then ran 2 tasks: The first task resizes and reformats the image, and the second task uploads the image to an AWS S3 bucket.
In our [previous post](/content/blog/image-processing-workflow-with-conductor) on image processing workflows, we built a Netflix Conductor workflow that took an image input, and then ran 2 tasks: The first task resizes and reformats the image, and the second task uploads the image to an AWS S3 bucket.

With today's varied screen sizes, and varied browser support, it is a common requirement that the image processing pipeline must create multiple images with different sizes and formats of each image.

Expand All @@ -16,7 +16,7 @@ In this post, our workflow will create 2 versions of the same image - a jpg and

<!-- truncate -->

> NOTE: This demo is provided to explain the FORK task in Conductor, but is not the best workflow to generate multiple images. For that - please read the [Image processing with dynamic workflows](image-processing-multiple-images-dynamic) post.
> NOTE: This demo is provided to explain the FORK task in Conductor, but is not the best workflow to generate multiple images. For that - please read the [Image processing with dynamic workflows](/content/blog/image-processing-multiple-images-dynamic) post.

## Getting Started

Expand Down
8 changes: 4 additions & 4 deletions blog/2022-02-02-image-processing-subworkflow.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,11 +5,11 @@ authors: doug
tags: [Netflix Conductor, Orkes, Conductor, orchestration, image processing, fork, subworkflow, tutorial,2022]
---

In our initial image processing workflow using Netflix Conductor, we [initially built a workflow](image-processing-workflow-with-conductor) that takes one image, resizes it and uploads it to S3.
In our initial image processing workflow using Netflix Conductor, we [initially built a workflow](/content/blog/image-processing-workflow-with-conductor) that takes one image, resizes it and uploads it to S3.

<img src="/content/img/blogassets/Simple-image-workflow.png" width="300" style={{paddingBottom: 40, paddingTop: 0}} />

In our 2nd post, we [utilized a fork to create two images in parallel](image-processing-multiple-images-forks). When building this workflow, we reused all of the tasks from the first workflow, connecting them in a way that allowing for parallel processing of two images at once.
In our 2nd post, we [utilized a fork to create two images in parallel](/content/blog/image-processing-multiple-images-forks). When building this workflow, we reused all of the tasks from the first workflow, connecting them in a way that allowing for parallel processing of two images at once.

<img src="/content/img/blogassets/workflow_fork.png" width="400" style={{paddingBottom: 40, paddingTop: 0}} />

Expand All @@ -31,7 +31,7 @@ There are a number of advantages to calling a sub-workflow:

## Creating our Subworkflow

We want to use the ```image_convert_resize``` workflow already created in our [simple workflow](image-processing-workflow-with-conductor) example. If you have not yet created this workflow (and the tasks that run under this workflow), you must first create a local Conductor instance, and then define this workflow (the instructions are in the blog post). It's also a good idea to test this workflow before using as a subworkflow - just to make sure that it is working as expected :D.
We want to use the ```image_convert_resize``` workflow already created in our [simple workflow](/content/blog/image-processing-workflow-with-conductor) example. If you have not yet created this workflow (and the tasks that run under this workflow), you must first create a local Conductor instance, and then define this workflow (the instructions are in the blog post). It's also a good idea to test this workflow before using as a subworkflow - just to make sure that it is working as expected :D.


## The (full) workflow
Expand All @@ -43,7 +43,7 @@ In this example, we'll utilize the ```image_convert_resize``` workflow as our su

### The workflow code

The overall workflow is essentially the same as the one built in the [forked workflow](image-processing-multiple-images-forks):
The overall workflow is essentially the same as the one built in the [forked workflow](/content/blog/image-processing-multiple-images-forks):

```
{
Expand Down