Skip to content
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.

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

Anchor text #239

Merged
merged 4 commits into from
Dec 15, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion docs/getting-started/install/orkes-conductor-community.md
Original file line number Diff line number Diff line change
Expand Up @@ -87,7 +87,7 @@ We welcome community contributions and PRs to this repository.

### Get Support
Use GitHub issue tracking for filing issues and Discussion Forum for any other questions, ideas or support requests.
Orkes (http://orkes.io) development team creates and maintains the Orkes-Conductor releases.
[Orkes](http://orkes.io) development team creates and maintains the Orkes-Conductor releases.

## License
Copyright 2022 Orkes, Inc.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ sidebar_position: 1
---
# Conductor Playground

Get started with Orkes Playground by creating a free account at [https://play.orkes.io](https://play.orkes.io).
Get started with [Orkes Playground](https://play.orkes.io) by creating a free account.

## What is Conductor Playground?
[Conductor Playground](https://play.orkes.io) is a free environment for developers to try out and explore more about Conductor. It is fully hosted by Orkes and is run as a multi-tenant cluster. Developers can use Playground to get familiarized with what Conductor offers and it is NOT intended for running production workflows. For running Conductor orchestration & workflows in production, we recommend the following:
Expand Down
4 changes: 1 addition & 3 deletions docs/getting-started/run/running-first-worker.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,11 +6,9 @@ sidebar_position: 2

In this article we will explore how you can get your first worker task running.

We are hosting the code used in this article in the following location. You can clone and use it as a reference
We are hosting the code used in this article [here](https://github.com/orkes-io/orkesworkers). You can clone and use it as a reference
locally.

#### https://github.com/orkes-io/orkesworkers

In the first codelab [Running your First Workflow](/content/docs/getting-started/run/running-first-workflow), we created a simple workflow that used a HTTP [System Task](/content/docs/getting-started/concepts/system-tasks) to run our workflow. System tasks run on the Conductor server - making commonly used functions easy to deploy in your workflow. Now it's time to explore how to run a
custom worker that you will implement yourself.

Expand Down
4 changes: 2 additions & 2 deletions docs/getting-started/run/running-first-workflow.md
Original file line number Diff line number Diff line change
Expand Up @@ -174,9 +174,9 @@ POST /api/workflow/<WorkflowName>

```

* Orkes Playground: [https://play.orkes.io/swagger-ui/index.html?configUrl=/api-docs/swagger-config#/workflow-resource/startWorkflow_1](https://play.orkes.io/swagger-ui/index.html?configUrl=/api-docs/swagger-config#/workflow-resource/startWorkflow_1)
* [Orkes Playground](https://play.orkes.io/swagger-ui/index.html?configUrl=/api-docs/swagger-config#/workflow-resource/startWorkflow_1)

* Local: [http://localhost:8080/swagger-ui/index.html?configUrl=/api-docs/swagger-config#/workflow-resource/startWorkflow_1](http://localhost:8080/swagger-ui/index.html?configUrl=/api-docs/swagger-config#/workflow-resource/startWorkflow_1)
* [Local](http://localhost:8080/swagger-ui/index.html?configUrl=/api-docs/swagger-config#/workflow-resource/startWorkflow_1)

![Swagger UI - Metadata - Workflow - Run](/img/tutorial/metadataWorkflowRun.png)

Expand Down