Go to file
2021-06-02 16:08:31 +02:00
.github/workflows Refactoring Webpack files to remove prod file. The prod file is now inferred from the NODE_ENV variable. 2021-05-12 11:28:21 +02:00
back Merge pull request #1020 from thecodingmachine/dependabot/npm_and_yarn/back/hosted-git-info-2.8.9 2021-05-26 15:49:03 +02:00
benchmark Bump hosted-git-info from 2.8.8 to 2.8.9 in /benchmark 2021-05-10 16:57:51 +00:00
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 2021-03-31 16:00:14 +02:00
docs Improving Changelog 2021-05-10 19:01:29 +02:00
front Save zoom level of the game and restore it when quitting the login scenes 2021-06-02 16:08:31 +02:00
maps Adding map test helpCameraSetting 2021-06-01 11:52:19 +02:00
messages Merge pull request #1026 from thecodingmachine/dependabot/npm_and_yarn/messages/hosted-git-info-2.8.9 2021-05-26 15:49:57 +02:00
pusher Merge pull request #1038 from thecodingmachine/dependabot/npm_and_yarn/pusher/lodash-4.17.21 2021-05-26 15:50:34 +02:00
uploader Bump hosted-git-info from 2.8.8 to 2.8.9 in /uploader 2021-05-10 16:57:50 +00:00
website Merge branch 'develop' of github.com:thecodingmachine/workadventure into fix/deploy-cleanup 2021-02-01 14:00:07 +01:00
.dockerignore *: Dockerfiles cleanup, docker-compose.prod.yaml 2021-01-12 22:32:37 +01:00
.env.template FEATURE: added the env variable DISABLE_DIRTY_CHECKS 2021-05-17 14:47:34 +02:00
.gitignore added: mate bottle accessorie 2020-11-20 11:49:08 +01:00
CHANGELOG.md Migrating LoginScene to Svelte 2021-05-31 17:03:29 +02:00
deeployer.libsonnet added back automatic deploy of staging 3 2021-05-10 12:44:35 +02:00
docker-compose.single-domain.yaml FEATURE: added the env variable DISABLE_DIRTY_CHECKS 2021-05-17 14:47:34 +02:00
docker-compose.yaml FEATURE: added the env variable DISABLE_DIRTY_CHECKS 2021-05-17 14:47:34 +02:00
README-INTRO.jpg Adding demo to README 2020-06-14 12:33:23 +02:00
README.md Merge pull request #687 from malteriechmann/patch-1 2021-04-29 10:39:47 +02:00
Vagrantfile.template Update vagrant template 2020-12-16 16:39:34 +01:00

Discord

WorkAdventure landscape image

Demo here : https://workadventu.re/.

Work Adventure

Work Adventure is a web-based collaborative workspace for small to medium teams (2-100 people) presented in the form of a 16-bit video game.

In Work Adventure, you can move around your office and talk to your colleagues (using a video-chat feature that is triggered when you move next to a colleague).

Setting up a development environment

Install Docker.

Run:

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

127.0.0.1 workadventure.localhost

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.

Prerequisites

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.