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

DEVLIB-1233: Rename Compute@Edge to Compute #9

Merged
merged 2 commits into from
Oct 25, 2023
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
24 changes: 12 additions & 12 deletions Cargo.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion Cargo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -10,4 +10,4 @@ publish = false
debug = 1

[dependencies]
fastly = "0.9.4"
fastly = "0.9.8"
10 changes: 5 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,22 +1,22 @@
# Compute@Edge WebSockets starter kit for Rust
# Fastly Compute WebSockets starter kit for Rust

[![Deploy to Fastly](https://deploy.edgecompute.app/button)](https://deploy.edgecompute.app/deploy)

Learn about Fastly Compute@Edge with WebSockets using a basic starter that sends connections to a backend.
Learn about Fastly Compute with WebSockets using a basic starter that sends connections to a backend.

Note: The WebSockets feature handles passthrough connections only. If you want to handle WebSocket connections from clients without having to run a WebSocket backend, see the [Fanout Starter Kit](https://github.com/fastly/compute-starter-kit-rust-fanout).

**For more details about this and other starter kits for Compute@Edge, see the [Fastly Developer Hub](https://developer.fastly.com/solutions/starters/)**.
**For more details about this and other starter kits for Compute, see the [Fastly Developer Hub](https://developer.fastly.com/solutions/starters/)**.

## Setup

The app expects a configured backend named `backend` that points to a WebSocket server. For example, if the WebSocket server is available at domain `websockets.example.com`, then you'll need to create a backend on your Compute@Edge service named `backend` with the destination host set to `websockets.example.com` and port 443. Also set 'Override Host' to the same host value.
The app expects a configured backend named `backend` that points to a WebSocket server. For example, if the WebSocket server is available at domain `websockets.example.com`, then you'll need to create a backend on your Compute service named `backend` with the destination host set to `websockets.example.com` and port 443. Also set 'Override Host' to the same host value.

After deploying the app and setting up the backend configuration, all connections received by the service will be passed to the backend.

## Note

This app is not currently supported in Fastly's [local development server](https://developer.fastly.com/learning/compute/testing/#running-a-local-testing-server), as the development server does not support WebSockets features. To experiment with WebSockets, you will need to publish this project to your Fastly Compute@Edge service, using the `fastly compute publish` command.
This app is not currently supported in Fastly's [local development server](https://developer.fastly.com/learning/compute/testing/#running-a-local-testing-server), as the development server does not support WebSockets features. To experiment with WebSockets, you will need to publish this project to your Fastly Compute service, using the `fastly compute publish` command.

## Security issues

Expand Down