maps: Serves the 'map' files via an apache server.pusher: The pusher component is in charge of accepting WebSocket and HTTP connections from the front and forwarding them to the correct "api" server (or to the "admin").Has sprites for characters, login-screens, menu's, etc. Runs code for the interface part of the game. front: based on a 'node-js' image from TheCodingMachine docker-repo.This guide contains info about this, later. Understanding what it does can be crucial to getting work-adventure and jitsi to work. This is an auto-configuring proxy-service that can be crucial in getting things to run smoothly. reverse-proxy: a 'traefik:v2.0' container from the public docker repo's.(more about this later).īy default, the docker-compose file provisions the following containers: There is a '.env.template' file that should be copied to '.env' and edited for settings. You do not need to know exactly the role of each container to get it to work with the install-guide supplied later, but it is handy to understand 'reverse-proxy', 'front' and 'maps', mainly. Work-adventure is found as a project deployed through 'docker-compose'. It is important to realize that this installation-guide replaces the default docker-compose.yaml files shipped with the projects and introduces a third one, enabling splitting off 'traefik' and 'coturn' from Work-adventure, making it easier to re-use these and manage them seperately from either Jitsi and/or Work-Adventure. This section lists the parts as you find them on their respective GITHUB repos. This guide hopes to give some aid in understanding and configuring the infra. This is true of Work-Adventure itself which starts 4 service-containers all on its own but becomes even more clear when you also want to host the JITSI-instance locally (instead of relying on ) and you want to use ssl-certs to make things work properly, as webrtc and CORS is rather picky about non-https content loaded into https-enabled sites.Īll of the above can make an installation of work-adventure (with, or without Jitsi locally) a challenging endevour. The challenge for newcomers to docker comes with the way that the software is composed from multiple moving parts that are all required to be started alongside eachother. While the mechanism works well, it lacks instructions on how to configure and run the software in a publically-accessible context instead of just on 'workadventure.localhost' as the README.MD explains you how to do. The API is documented however, and creation of a custom backend seems relatively easy to do.īy default, installing the github-provided release is most easily done via their included 'docker-compose.yaml', as listed on the README.MD file in the repo. The release is fully functional, apart from lacking an authentication/management backend that would allow restricting access, moderation, administrator-rights, etc. The software has been designed by and is released on their as open source. It allows text-based messaging, has direct web-rtc enabled video/audio chats available for up to 4 people in eachother's vincinity, as well as providign mechanisms to have 'rooms' of more participants by leveraging a server of choice. can be described as a spatially-enabled meet/chat space in an environment that is akin to 16-bit RPG games from the 90's. Since early 2021, Techinc hosts an 'instance' of Work-Adventure on. 4.2 Running Traefik and configuring docker-networking.
0 kommentar(er)
