_Bastler/partey_workadventure
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
2,534 Commits 2 Branches 0 Tags 47 MiB
TypeScript 78.1%
Svelte 12.7%
HTML 2.7%
CSS 1.5%
SCSS 1.5%
Other 3.4%
315fe7ca82
Go to file
David Négrier 315fe7ca82
Adding a "font-family" property for text objects. (#1311) 
- Tiled displays your system fonts.
- Computers have different sets of fonts. Therefore, browsers never rely on system fonts
- Which means if you select a font in Tiled, it is quite unlikely it will render properly in WorkAdventure

To circumvent this problem, in your text object in Tiled, you can now add an additional property: `font-family`.

The `font-family` property can contain any "web-font" that can be loaded by your browser.

This allows us to use the "Press Start 2P" 8px font in text objects, which renders way better than the default "Sans serif" font of your browser.
2021-07-29 17:49:51 +02:00
.github/workflows Fixing NPM package generation 2021-06-30 10:15:55 +02:00
.husky Setting up lint-staged on front and back 2021-06-23 16:45:38 +02:00
back Merge branch 'master' into develop 2021-07-28 12:37:14 +02:00
benchmark Bump ws from 7.3.1 to 7.4.6 in /benchmark 2021-06-17 09:25:14 +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 Adding a "font-family" property for text objects. (#1311) 2021-07-29 17:49:51 +02:00
front Adding a "font-family" property for text objects. (#1311) 2021-07-29 17:49:51 +02:00
maps Adding a "font-family" property for text objects. (#1311) 2021-07-29 17:49:51 +02:00
messages Adding support for "readableBy" and "writableBy" in back 2021-07-19 10:16:43 +02:00
pusher Fix some typos (found by codespell) (#1316) 2021-07-27 14:29:09 +02:00
uploader Merge pull request #576 from Informatic/fix/dependencies-cleanup 2021-06-17 11:24:26 +02: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 husky to gitignore 2021-06-25 18:07:03 +02:00
CHANGELOG.md Fix some typos (found by codespell) (#1316) 2021-07-27 14:29:09 +02:00
CONTRIBUTING.md setProperty function doesn't set an empty array if property doesn't exist 2021-07-02 14:40:18 +02:00
deeployer.libsonnet Adding support to persist variables in Redis 2021-07-19 16:23:16 +02:00
docker-compose.single-domain.yaml Adding support to persist variables in Redis 2021-07-19 16:23:16 +02:00
docker-compose.yaml Adding support to persist variables in Redis 2021-07-19 16:23:16 +02:00
package.json Setting up prettier 2021-06-23 10:10:53 +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
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 Merging master into develop 2021-06-29 18:39:43 +02:00

README.md

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.