You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
Valdo f6fcb37d91
Updated README (logo, map, wording) (#1485)
Co-authored-by: Valdo Romao <>
2 years ago
.github/workflows Fixing Posthog env var 2 years ago
.husky Setting up lint-staged on front and back 2 years ago
back Bump axios from 0.21.1 to 0.21.2 in /back 2 years ago
benchmark Release v1.4.15 (#1411) 2 years ago
contrib/docker [Breaking change] UPLOADER_URL and ADMIN_URL are now true URLs (and not only host name) and API_URL is replaced by PUSHER_URL 2 years ago
docs Merge branch 'master' of 2 years ago
front Remove audio manager range volume control by keys (#1489) 2 years ago
maps Removed old maps and add starter-kit map 2 years ago
messages Release v1.4.15 (#1411) 2 years ago
pusher Manage redirect URL from admin and save in hydra via pusher (#1492) 2 years ago
uploader Release v1.4.15 (#1411) 2 years ago
.dockerignore *: Dockerfiles cleanup, 2 years ago
.env.template Merge pull request #1480 from ValdoTR/maps 2 years ago
.gitignore added husky to gitignore 2 years ago Updating Changelog 2 years ago setProperty function doesn't set an empty array if property doesn't exist 2 years ago
README-LOGO.svg Updated README (logo, map, wording) (#1485) 2 years ago
README-MAP.png Updated README (logo, map, wording) (#1485) 2 years ago Updated README (logo, map, wording) (#1485) 2 years ago Create 2 years ago
Vagrantfile.template Update vagrant template 2 years ago
deeployer.libsonnet FIX: removed admin url from deeployer on develop and master and changed starter map 2 years ago
docker-compose.single-domain.yaml FIX: bomp the node version of pusher 2 years ago
docker-compose.yaml FIX: bomp the node version of pusher 2 years ago
package-lock.json Merge remote-tracking branch 'remotes/upstream/develop' into trigger-message-refv3 2 years ago
package.json Update package.json (#1344) 2 years ago
yarn.lock Merging master into develop 2 years ago


WorkAdventure logo WorkAdventure office image

Live demo here.


WorkAdventure is a web-based collaborative workspace presented in the form of a 16-bit video game.

In WorkAdventure you can move around your office and talk to your colleagues (using a video-chat system, triggered when you approach someone).

See more features for your virtual office:

Setting up a development environment

Install Docker.


cp .env.template .env
docker-compose up -d

The environment will start.

You should now be able to browse to http://play.workadventure.localhost/ and see the application. You can view the dashboard at http://workadventure.localhost:8080/

Note: on some OSes, you will need to add this line to your /etc/hosts file:

/etc/hosts workadventure.localhost

Note: If on the first run you get a page with "network error". Try to docker-compose stop , then docker-compose start. Note 2: If you are still getting "network error". Make sure you are authorizing the self-signed certificate by entering https://pusher.workadventure.testing and accepting them.

MacOS developers, your environment with Vagrant

If you are using MacOS, you can increase Docker performance using Vagrant. If you want more explanations, you can read this medium article.


First steps

Create a config file Vagrantfile from Vagrantfile.template

cp Vagrantfile.template Vagrantfile

In Vagrantfile, update VM_HOST_PATH with the local project path of your machine.

#VM_HOST_PATH# => your local machine path to the project

(run pwd and copy the path in this variable)

To start your VM Vagrant, run:

Vagrant up

To connect to your VM, run:

Vagrant ssh

To start project environment, run

docker-compose up

You environment runs in you VM Vagrant. When you want stop your VM, you can run:

Vagrant halt

If you want to destroy, you can run

Vagrant destroy

Available commands

  • Vagrant up: start your VM Vagrant.
  • Vagrant reload: reload your VM Vagrant when you change Vagrantfile.
  • Vagrant ssh: connect on your VM Vagrant.
  • Vagrant halt: stop your VM Vagrant.
  • Vagrant destroy: delete your VM Vagrant.

Setting up a production environment

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 directory.