Skip to content

Commit

Permalink
Replace ghcr.io/restatedev/restate-dist with docker.io/restatedev/res…
Browse files Browse the repository at this point in the history
…tate
  • Loading branch information
tillrohrmann committed Nov 28, 2023
1 parent f1a1da2 commit 6b6d7c0
Show file tree
Hide file tree
Showing 6 changed files with 88 additions and 89 deletions.
4 changes: 2 additions & 2 deletions docs/quickstart.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ This starts the greeter service on port 9080.
Run the Restate Docker container:

```shell
docker run --name restate_dev --rm -d --network=host ghcr.io/restatedev/restate-dist:VAR::RESTATE_DIST_VERSION
docker run --name restate_dev --rm -d --network=host docker.io/restatedev/restate:VAR::RESTATE_DIST_VERSION
```

Register the service:
Expand All @@ -74,7 +74,7 @@ After executing this curl request, you should see the discovered services and me
Run the Restate Docker container:

```shell
docker run --name restate_dev --rm -d -p 8080:8080 -p 9070:9070 -p 9071:9071 ghcr.io/restatedev/restate-dist:VAR::RESTATE_DIST_VERSION
docker run --name restate_dev --rm -d -p 8080:8080 -p 9070:9070 -p 9071:9071 docker.io/restatedev/restate:VAR::RESTATE_DIST_VERSION
```

Register the services:
Expand Down
3 changes: 1 addition & 2 deletions docs/restate/deployment.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@ spec:
- name: github
containers:
- name: restate
image: ghcr.io/restatedev/restate-dist:VAR::RESTATE_DIST_VERSION
image: docker.io/restatedev/restate:VAR::RESTATE_DIST_VERSION
env:
- name: RESTATE_TRACING__LOG_FORMAT
value: Json
Expand Down Expand Up @@ -104,4 +104,3 @@ You will also need to create an image pull secret using a classic github persona
```bash
$ kubectl create secret docker-registry github --docker-server=ghcr.io --docker-username=<your-github-username> --docker-password=<your-personal-access-token>
```

10 changes: 5 additions & 5 deletions docs/restate/tracing.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,14 +48,14 @@ Then launch Restate with the tracing endpoint defined as an environment variable
<TabItem value="lin" label="Linux">

```shell
docker run --name restate_dev --rm -d -e RESTATE_OBSERVABILITY__TRACING__ENDPOINT=http://localhost:4317 --network=host ghcr.io/restatedev/restate-dist:VAR::RESTATE_DIST_VERSION
docker run --name restate_dev --rm -d -e RESTATE_OBSERVABILITY__TRACING__ENDPOINT=http://localhost:4317 --network=host docker.io/restatedev/restate:VAR::RESTATE_DIST_VERSION
```

</TabItem>
<TabItem value="mac" label="macOS">

```shell
docker run --name restate_dev --rm -d -e RESTATE_OBSERVABILITY__TRACING__ENDPOINT=http://host.docker.internal:4317 -p 8080:8080 -p 9070:9070 -p 9071:9071 ghcr.io/restatedev/restate-dist:VAR::RESTATE_DIST_VERSION
docker run --name restate_dev --rm -d -e RESTATE_OBSERVABILITY__TRACING__ENDPOINT=http://host.docker.internal:4317 -p 8080:8080 -p 9070:9070 -p 9071:9071 docker.io/restatedev/restate:VAR::RESTATE_DIST_VERSION
```

</TabItem>
Expand Down Expand Up @@ -84,10 +84,10 @@ The traces contain detailed information about the context calls that were done d

The initial `ingress_invoke` spans show when the gRPC/Connect HTTP request was received by Restate. The `invoke` span beneath it shows when Restate invoked the service endpoint to process the request.

The tags of the spans contain the metadata of the context calls (e.g. call arguments, invocation id).
The tags of the spans contain the metadata of the context calls (e.g. call arguments, invocation id).

Check warning on line 87 in docs/restate/tracing.md

View workflow job for this annotation

GitHub Actions / Test build

[vale] reported by reviewdog 🐶 [Google.Parens] Use parentheses judiciously. Raw Output: {"message": "[Google.Parens] Use parentheses judiciously.", "location": {"path": "docs/restate/tracing.md", "range": {"start": {"line": 87, "column": 65}}}, "severity": "INFO"}

Check failure on line 87 in docs/restate/tracing.md

View workflow job for this annotation

GitHub Actions / Test build

[vale] reported by reviewdog 🐶 [Google.Latin] Use 'for example' instead of 'e.g.'. Raw Output: {"message": "[Google.Latin] Use 'for example' instead of 'e.g.'.", "location": {"path": "docs/restate/tracing.md", "range": {"start": {"line": 87, "column": 66}}}, "severity": "ERROR"}

When a service invokes another service, the child invocation is linked automatically to the parent invocation, as you can see in the image.
Note that the spans of one-way calls are shown as separate traces. The parent invocation only shows that the one-way call was scheduled, not its entire tracing span.
Note that the spans of one-way calls are shown as separate traces. The parent invocation only shows that the one-way call was scheduled, not its entire tracing span.

Check warning on line 90 in docs/restate/tracing.md

View workflow job for this annotation

GitHub Actions / Test build

[vale] reported by reviewdog 🐶 [write-good.E-Prime] Try to avoid using 'are'. Raw Output: {"message": "[write-good.E-Prime] Try to avoid using 'are'.", "location": {"path": "docs/restate/tracing.md", "range": {"start": {"line": 90, "column": 38}}}, "severity": "INFO"}

Check warning on line 90 in docs/restate/tracing.md

View workflow job for this annotation

GitHub Actions / Test build

[vale] reported by reviewdog 🐶 [Google.Passive] In general, use active voice instead of passive voice ('are shown'). Raw Output: {"message": "[Google.Passive] In general, use active voice instead of passive voice ('are shown').", "location": {"path": "docs/restate/tracing.md", "range": {"start": {"line": 90, "column": 38}}}, "severity": "INFO"}

Check warning on line 90 in docs/restate/tracing.md

View workflow job for this annotation

GitHub Actions / Test build

[vale] reported by reviewdog 🐶 [write-good.Passive] 'are shown' may be passive voice. Use active voice if you can. Raw Output: {"message": "[write-good.Passive] 'are shown' may be passive voice. Use active voice if you can.", "location": {"path": "docs/restate/tracing.md", "range": {"start": {"line": 90, "column": 38}}}, "severity": "WARNING"}

Check warning on line 90 in docs/restate/tracing.md

View workflow job for this annotation

GitHub Actions / Test build

[vale] reported by reviewdog 🐶 [write-good.Weasel] 'only' is a weasel word! Raw Output: {"message": "[write-good.Weasel] 'only' is a weasel word!", "location": {"path": "docs/restate/tracing.md", "range": {"start": {"line": 90, "column": 90}}}, "severity": "WARNING"}

Check warning on line 90 in docs/restate/tracing.md

View workflow job for this annotation

GitHub Actions / Test build

[vale] reported by reviewdog 🐶 [write-good.E-Prime] Try to avoid using 'was'. Raw Output: {"message": "[write-good.E-Prime] Try to avoid using 'was'.", "location": {"path": "docs/restate/tracing.md", "range": {"start": {"line": 90, "column": 123}}}, "severity": "INFO"}

Check warning on line 90 in docs/restate/tracing.md

View workflow job for this annotation

GitHub Actions / Test build

[vale] reported by reviewdog 🐶 [Google.Passive] In general, use active voice instead of passive voice ('was scheduled'). Raw Output: {"message": "[Google.Passive] In general, use active voice instead of passive voice ('was scheduled').", "location": {"path": "docs/restate/tracing.md", "range": {"start": {"line": 90, "column": 123}}}, "severity": "INFO"}

Check warning on line 90 in docs/restate/tracing.md

View workflow job for this annotation

GitHub Actions / Test build

[vale] reported by reviewdog 🐶 [write-good.Passive] 'was scheduled' may be passive voice. Use active voice if you can. Raw Output: {"message": "[write-good.Passive] 'was scheduled' may be passive voice. Use active voice if you can.", "location": {"path": "docs/restate/tracing.md", "range": {"start": {"line": 90, "column": 123}}}, "severity": "WARNING"}
To see this information, search for the trace of the one-way call by filtering on the invocation id tag:
```
restate.invocation.id="T4pIkIJIGAsBiiGDV2dxK7PkkKnWyWHE"
Expand All @@ -97,4 +97,4 @@ restate.invocation.id="T4pIkIJIGAsBiiGDV2dxK7PkkKnWyWHE"

Traces export attributes and tags that correlate the trace with the service and/or invocation. For example, in the Jaeger UI, you can filter on the invocation id (`restate.invocation.id`) or any other tag:

![Jaeger invocation id search](/img/jaeger_invocationid_search_handler.png)
![Jaeger invocation id search](/img/jaeger_invocationid_search_handler.png)
4 changes: 2 additions & 2 deletions docs/services/deployment/lambda.md
Original file line number Diff line number Diff line change
Expand Up @@ -181,11 +181,11 @@ see https://github.com/awslabs/aws-sdk-rust/issues/703#issuecomment-1811480196.

- On Linux
```shell
docker run -e AWS_PROFILE -v ~/.aws/:/root/.aws --name restate_dev --rm -d --network=host ghcr.io/restatedev/restate-dist:VAR::RESTATE_DIST_VERSION
docker run -e AWS_PROFILE -v ~/.aws/:/root/.aws --name restate_dev --rm -d --network=host docker.io/restatedev/restate:VAR::RESTATE_DIST_VERSION
```
- On macOS:
```shell
docker run -e AWS_PROFILE -v ~/.aws/:/root/.aws --name restate_dev --rm -d -p 8080:8080 -p 9070:9070 -p 9071:9071 ghcr.io/restatedev/restate-dist:VAR::RESTATE_DIST_VERSION
docker run -e AWS_PROFILE -v ~/.aws/:/root/.aws --name restate_dev --rm -d -p 8080:8080 -p 9070:9070 -p 9071:9071 docker.io/restatedev/restate:VAR::RESTATE_DIST_VERSION
```

Consult the runtime logs via `docker logs restate_dev`.
Expand Down
10 changes: 5 additions & 5 deletions docs/tour.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ As we go, you will discover how Restate can help you with some intricacies in th

This guide is written for:
- Typescript SDK version: `@restatedev/restate-sdk:VAR::TYPESCRIPT_SDK_VERSION`
- Restate runtime Docker image: `restate-dist:VAR::RESTATE_DIST_VERSION`
- Restate runtime Docker image: `restatedev/restate:VAR::RESTATE_DIST_VERSION`

## 🚀 Let's get started!

Expand Down Expand Up @@ -65,14 +65,14 @@ Launch the runtime:
<TabItem value="lin" label="Linux">

```shell
docker run --name restate_dev --rm -d --network=host ghcr.io/restatedev/restate-dist:VAR::RESTATE_DIST_VERSION
docker run --name restate_dev --rm -d --network=host docker.io/restatedev/restate:VAR::RESTATE_DIST_VERSION
```

</TabItem>
<TabItem value="mac" label="macOS">

```shell
docker run --name restate_dev --rm -d -p 8080:8080 -p 9070:9070 -p 9071:9071 ghcr.io/restatedev/restate-dist:VAR::RESTATE_DIST_VERSION
docker run --name restate_dev --rm -d -p 8080:8080 -p 9070:9070 -p 9071:9071 docker.io/restatedev/restate:VAR::RESTATE_DIST_VERSION
```

</TabItem>
Expand Down Expand Up @@ -1332,14 +1332,14 @@ Then restart the runtime with the tracing endpoint defined as an environment var
<TabItem value="lin" label="Linux">

```shell
docker run --name restate_dev --rm -d -e RESTATE_OBSERVABILITY__TRACING__ENDPOINT=http://localhost:4317 --network=host ghcr.io/restatedev/restate-dist:VAR::RESTATE_DIST_VERSION
docker run --name restate_dev --rm -d -e RESTATE_OBSERVABILITY__TRACING__ENDPOINT=http://localhost:4317 --network=host docker.io/restatedev/restate:VAR::RESTATE_DIST_VERSION
```

</TabItem>
<TabItem value="mac" label="macOS">

```shell
docker run --name restate_dev --rm -d -e RESTATE_OBSERVABILITY__TRACING__ENDPOINT=http://host.docker.internal:4317 -p 8080:8080 -p 9070:9070 -p 9071:9071 ghcr.io/restatedev/restate-dist:VAR::RESTATE_DIST_VERSION
docker run --name restate_dev --rm -d -e RESTATE_OBSERVABILITY__TRACING__ENDPOINT=http://host.docker.internal:4317 -p 8080:8080 -p 9070:9070 -p 9071:9071 docker.io/restatedev/restate:VAR::RESTATE_DIST_VERSION
```

</TabItem>
Expand Down
Loading

0 comments on commit 6b6d7c0

Please sign in to comment.