mirror of
https://github.com/nestriness/nestri.git
synced 2025-12-12 16:55:37 +02:00
060718d8b0
>Adds `maitred` in charge of handling automated game installs, updates,
and even execution.
>Not only that, we have the hosted stuff here
>- [x] AWS Task on ECS GPUs
>- [ ] Add a service to listen for game starts and stops
(docker-compose.yml)
>- [x] Add a queue for requesting a game to start
>- [x] Fix up the play/watch UI
>TODO:
>- Add a README
>- Add an SST docs
Edit:
- This adds a new landing page, updates the homepage etc etc
>I forgot what the rest of the updated stuff are 😅
33 lines
1.1 KiB
TypeScript
33 lines
1.1 KiB
TypeScript
// This is for the websocket/MQTT endpoint that helps the API communicate with the container
|
|
// [API] <-> party <-websocket-> container
|
|
// The container is it's own this, and can listen to Websocket connections to start or stop a Steam Game
|
|
|
|
// import { authFingerprintKey } from "./auth";
|
|
// import { ecsCluster, gpuTaskDefinition } from "./cluster";
|
|
|
|
// export const party = new sst.aws.Realtime("Party", {
|
|
// authorizer: "packages/functions/src/party/authorizer.handler"
|
|
// });
|
|
|
|
// export const partyFn = new sst.aws.Function("NestriPartyFn", {
|
|
// handler: "packages/functions/src/party/create.handler",
|
|
// // link: [queue],
|
|
// link: [authFingerprintKey],
|
|
// environment: {
|
|
// TASK_DEFINITION: gpuTaskDefinition.arn,
|
|
// // AUTH_FINGERPRINT: authFingerprintKey.result,
|
|
// ECS_CLUSTER: ecsCluster.arn,
|
|
// },
|
|
// permissions: [
|
|
// {
|
|
// effect: "allow",
|
|
// actions: ["ecs:RunTask"],
|
|
// resources: [gpuTaskDefinition.arn]
|
|
// }
|
|
// ],
|
|
// url: true,
|
|
// });
|
|
|
|
// export const outputs = {
|
|
// partyFunction: partyFn.url
|
|
// }
|