Go to file
2022-02-27 13:59:05 +01:00
.github/workflows Merge branch 'develop' into vite 2022-02-19 20:08:50 +01:00
.husky Adding Prettier in messages 2021-12-16 16:40:50 +01:00
back rename images 2022-02-26 11:19:48 +01:00
benchmark Bump path-parse from 1.0.6 to 1.0.7 in /benchmark 2021-09-01 15:48:20 +00:00
contrib/docker Merge branch 'develop' of github.com:thecodingmachine/workadventure into develop 2022-02-16 20:25:12 +01:00
docs Documents the meetingRoomLabel property 2022-02-23 18:27:16 +01:00
front orig. formatting 2022-02-27 13:59:05 +01:00
maps update docs and remove references to testcafe 2022-02-18 16:11:26 +01:00
messages Bump shelljs from 0.8.4 to 0.8.5 in /messages 2022-01-15 06:59:54 +00:00
pusher rename images 2022-02-26 11:19:48 +01:00
tests load ADMIN_API_TOKEN with dotenv-cli 2022-02-18 16:37:50 +01:00
uploader rename images 2022-02-26 11:19:48 +01:00
.dockerignore *: Dockerfiles cleanup, docker-compose.prod.yaml 2021-01-12 22:32:37 +01:00
.env.template Merge branch 'develop' of github.com:thecodingmachine/workadventure 2021-11-16 10:56:33 +01:00
.gitignore update readme 2021-08-23 08:22:13 +02:00
CHANGELOG.md Add multi co website to the changelog 2021-10-27 09:47:15 +02:00
CONTRIBUTING.md update docs and remove references to testcafe 2022-02-18 16:11:26 +01:00
deeployer.libsonnet Continuous Deployment: add connect to admin 2022-02-17 15:04:51 +01:00
docker-compose.e2e.yml base front production image on official nginx image 2022-02-25 20:32:10 +01:00
docker-compose.single-domain.yaml Merge branch 'master' of github.com:thecodingmachine/workadventure into develop 2021-11-30 15:13:36 +01:00
docker-compose.yaml remove unused LIVE_RELOAD variable 2022-02-15 20:28:52 +01:00
package-lock.json Merge remote-tracking branch 'remotes/upstream/develop' into trigger-message-refv3 2021-07-02 18:49:22 +02:00
package.json Revert "Improving log messages" 2021-11-24 16:20:07 +01:00
README.md update readme 2022-02-02 11:09:45 +01:00
SECURITY.md Create SECURITY.md 2021-06-23 15:26:17 +02:00
Vagrantfile.template Update vagrant template 2020-12-16 16:39:34 +01:00
yarn.lock yarn.lock update 2022-02-07 13:47:33 +01:00

This is a fork of WorkAdventure with some adjustment and changes for production environment for Bastelei e. V. Partey

WorkAdventure

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: https://workadventu.re/virtual-office

Community resources

Check out resources developed by the WorkAdventure community at awesome-workadventure

Setting up a development environment

Install Docker.

Run:

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

127.0.0.1 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.localhost 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.

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 production environment of Partey is based on a single-domain deployment with some changed, minimized Dockerfiles based on the fork workadventure-xce. An example can be found in contrib/docker/docker-compose.single-domain.prod.yaml. To create a non-single-domain based environment, please adopt settings from the below WorkAdventure provided file yourself. The changed Dockerfiles won't work directly with the file below!

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.