Adding link to the docker-compose prod file in README.
This commit is contained in:
parent
246174c365
commit
b9c839a87d
@ -15,7 +15,7 @@ In Work Adventure, you can move around your office and talk to your colleagues (
|
|||||||
triggered when you move next to a colleague).
|
triggered when you move next to a colleague).
|
||||||
|
|
||||||
|
|
||||||
## Getting started
|
## Setting up a development environment
|
||||||
|
|
||||||
Install Docker.
|
Install Docker.
|
||||||
|
|
||||||
@ -101,5 +101,7 @@ Vagrant destroy
|
|||||||
* `Vagrant halt`: stop your VM Vagrant.
|
* `Vagrant halt`: stop your VM Vagrant.
|
||||||
* `Vagrant destroy`: delete your VM Vagrant.
|
* `Vagrant destroy`: delete your VM Vagrant.
|
||||||
|
|
||||||
## Features developed
|
## Setting up a production environment
|
||||||
You have more details of features developed in back [README.md](./back/README.md).
|
|
||||||
|
The way you set up your production environment will highly depend on your servers.
|
||||||
|
We provide a production ready `docker-compose` file that you can use as a good starting point in the [contrib/docker](https://github.com/thecodingmachine/workadventure/tree/master/contrib/docker) directory.
|
||||||
|
@ -1,61 +0,0 @@
|
|||||||
# Back Features
|
|
||||||
|
|
||||||
## Login
|
|
||||||
To start your game, you must authenticate on the server back.
|
|
||||||
When you are authenticated, the back server return token and room starting.
|
|
||||||
```
|
|
||||||
POST => /login
|
|
||||||
Params :
|
|
||||||
email: email of user.
|
|
||||||
```
|
|
||||||
|
|
||||||
## Join a room
|
|
||||||
When a user is connected, the user can join a room.
|
|
||||||
So you must send emit `join-room` with information user:
|
|
||||||
```
|
|
||||||
Socket.io => 'join-room'
|
|
||||||
|
|
||||||
userId: user id of gamer
|
|
||||||
roomId: room id when user enter in game
|
|
||||||
position: {
|
|
||||||
x: position x on map
|
|
||||||
y: position y on map
|
|
||||||
}
|
|
||||||
```
|
|
||||||
All data users are stocked on socket client.
|
|
||||||
|
|
||||||
## Send position user
|
|
||||||
When user move on the map, you can share new position on back with event `user-position`.
|
|
||||||
The information sent:
|
|
||||||
```
|
|
||||||
Socket.io => 'user-position'
|
|
||||||
|
|
||||||
userId: user id of gamer
|
|
||||||
roomId: room id when user enter in game
|
|
||||||
position: {
|
|
||||||
x: position x on map
|
|
||||||
y: position y on map
|
|
||||||
}
|
|
||||||
```
|
|
||||||
All data users are updated on socket client.
|
|
||||||
|
|
||||||
## Receive positions of all users
|
|
||||||
The application sends position of all users in each room in every few 10 milliseconds.
|
|
||||||
The data will pushed on event `user-position`:
|
|
||||||
```
|
|
||||||
Socket.io => 'user-position'
|
|
||||||
|
|
||||||
[
|
|
||||||
{
|
|
||||||
userId: user id of gamer
|
|
||||||
roomId: room id when user enter in game
|
|
||||||
position: {
|
|
||||||
x: position x on map
|
|
||||||
y: position y on map
|
|
||||||
}
|
|
||||||
},
|
|
||||||
...
|
|
||||||
]
|
|
||||||
```
|
|
||||||
|
|
||||||
[<<< back](../README.md)
|
|
Loading…
Reference in New Issue
Block a user