_Bastler/partey_workadventure
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
ce1961e34e
partey_workadventure/pusher
History
Alexis Faizeau d1e8243c47
Zod EVERYWHERE (#2027) 
* Zod EVERYWHERE

* Add no-unused-vars rule to eslint in front

* Add no-unused-vars rule to eslint in pusher

* Add no-unused-vars rule to eslint in back

* Remove unused PlayerTexture guards

* Fix data providing on room connection

Co-authored-by: Alexis Faizeau <a.faizeau@workadventu.re>
2022-04-12 14:21:19 +02:00
..
data Change names of woka textures 2022-03-14 12:58:33 +01:00
src Zod EVERYWHERE (#2027) 2022-04-12 14:21:19 +02:00
tests Migrating away from the notion of public/private URL in WorkAdventure Github repository 2021-07-15 17:07:47 +02:00
.dockerignore Adding a Pusher container as a middleware/dispatcher between front and back 2020-11-26 17:53:30 +01:00
.eslintrc.json Zod EVERYWHERE (#2027) 2022-04-12 14:21:19 +02:00
.gitignore Adding a Pusher container as a middleware/dispatcher between front and back 2020-11-26 17:53:30 +01:00
.prettierignore Adding Prettier in messages 2021-12-16 16:40:50 +01:00
.prettierrc.json Making max line length to 120 2021-06-23 16:58:57 +02:00
Dockerfile Multi-platform images (#1924) 2022-03-08 11:21:17 +01:00
Dockerfile.prod *: Dockerfiles cleanup, docker-compose.prod.yaml 2021-01-12 22:32:37 +01:00
jasmine.json Adding a Pusher container as a middleware/dispatcher between front and back 2020-11-26 17:53:30 +01:00
LICENSE.txt Adding a Pusher container as a middleware/dispatcher between front and back 2020-11-26 17:53:30 +01:00
package.json Zod EVERYWHERE (#2027) 2022-04-12 14:21:19 +02:00
README.md Adding a Pusher container as a middleware/dispatcher between front and back 2020-11-26 17:53:30 +01:00
server.ts Revert "Improving log messages" 2021-11-24 16:20:07 +01:00
tsconfig.json Zod EVERYWHERE (#2027) 2022-04-12 14:21:19 +02:00
yarn.lock Zod EVERYWHERE (#2027) 2022-04-12 14:21:19 +02:00

README.md

Pusher

The pusher component is in charge of accepting WebSocket and HTTP connections from the front and forwarding them to the correct "api" server (or to the "admin").