Fix links in Live Profiles accelerator#1281
Conversation
✅ Deploy Preview for snowplow-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
dc37073 to
7a37d67
Compare
| - **Snowplow Collector and Snowbridge** for event processing and forwarding. | ||
| - **Live Viewer Backend** for managing real-time data with Kafka and DynamoDB. | ||
| - **Live Viewer Frontend** for visualizing real-time user activity on the web tracking application. | ||
| - **Snowplow Collector and Snowbridge** for event processing and forwarding |
|
|
||
| You explored how to: | ||
| 1. Use LocalStack to emulate AWS services for local development and testing | ||
| 2. Launch and interact with the system components, such as the Kafka UI and LocalStack UI |
There was a problem hiding this comment.
Haven't run the accelerator but does Localstack provide a UI in the free version?
| - Look into the output from Kafka and extend the Live Viewer to include information on the media being watched and the user. | ||
| - Replace Amazon DynamoDB with an alternative to be cloud agnostic, e.g. Google Bigtable or MongoDB. | ||
| - Look into the output from Kafka and extend the Live Viewer to include information on the media being watched and the user | ||
| - Replace Amazon DynamoDB with an alternative to be cloud agnostic, e.g. Google Bigtable or MongoDB |
There was a problem hiding this comment.
Maybe use Redis here instead of Google Bigtable? I get the sentiment but Bigtable isn't cloud agnostic (GCP only).
| ### Inspect Infrastructure with LocalStack UI | ||
| ### Inspect infrastructure with LocalStack UI | ||
|
|
||
| Visit the [LocalStack UI](https://app.localstack.cloud/) to inspect infrastructure components such as Kinesis and DynamoDB. Please note that a LocalStack account is required to view this. |
There was a problem hiding this comment.
Should we just remove this assuming that the user doesn't have a paid account?
Phil Catterall (phil-snowplow)
left a comment
There was a problem hiding this comment.
I'll give it a tick, but we might want to think about removing or reframing this accelerator, because it basically shows you how to build a basic version of the Signals profile store. We should either be directing people to use Signals instead, or use this as a way to illustrate how much work this is to do yourself vs. using Signals.

The example
.envfile in the related repo moved from to.env.exampleto./docker/.env.example. This PR is to update that link. Also updates the text to comply more with the style guide.