 Und dann freue ich mich, euch für den ersten Tag vorzustellen zu dürfen. Ich bin sehr glücklich, um dir zu zeigen, dass Defnope den Operator in der Linus und Unix, und wie die meisten von uns, er hat das Gefühl, dass wir uns in diesem Zusammenhang haben, unser eigenes Arbeitsadventure zu machen, um die Wunderungssymptome zu schaffen. Und er wird dir zeigen, wie du es dir selbst tun kannst. Danke. So, das ist mein Gespräch. Also, im Moment, die Dokumentation des Arbeitsadventures ist optimisabel. Ich habe mir realisiert, dass die meisten Leute mit diesem Problem haben. Man könnte es automatisieren und es ein bisschen mehr komfortibler haben. So, based on this, I built something. And now, I think it's really important to do a talk on this. So, what do you need from my solution? You need a VM or a VPS, a virtual private service. That's using a Debian 10 host. This is what I felt most comfortable with. Furthermore, you need a domain, which you can use and input subdomains. This domain is used so other people can reach your work adventure instance. And you might need a little basic knowledge of Linux, Debian and Ansible. So, what do you have to do? I guess you have a blank Debian machine and you configure all the domains you have. What kind of subdomains you have to configure? You can see in the readme of the repository and I will show you next. And then download the whole repository. In this repository, there's configurations you have to do to optimize the deployment process. For example, the domain you want to use. The room you want to use by standard. And what kind of user you want to use to connect via SSR to the host. And if you then use the Ansible Playbook, you have this command. And after that, you need to reboot it. Some packages are open that need to reboot. And as soon as the machine is back, you change to the opt-work-adventure-contract docker file. And then you start docker. So, what does Ansible do in this case? Debian 10 is up to testing. The host system is made late. There's packages that are installed. A user is set up. You can use to connect to the host. There's a lot of security settings that are optimized. Firewall rules, for example, configs for the SSH demon. That prevent the root user to connect via SSR to the host. These are all measures to make sure everything works fine. And you don't have to worry. After that, docker and docker-compose is installed. So you don't have many more issues there. After that, you download the work-adventure repository and it's prepared for you. Afterwards, you need a few config files. You don't have to do anything more to change it and you can start over right. How is work-adventure set up? Each function has one container. The main part is the reverse proxy. This is made with traffic. It's like a reverse proxy. But this is running inside of docker and connects to the container. This makes optimization possible. Some proxies can't do this. Furthermore, Let's Encrypt is installed and you don't have to care about that or where you can get the TLS certificate. And yeah, start and stop is realized using docker-compose. So, well, some people might think I'm in a hurry. How can I get work-adventure running? What I found out was that most difficult is to get the jason file connected that sets up the information for the TLS certificate, for example. Furthermore, you can have issues with the docker-socket that's not reachable. It should be at least readable, but I really set it to read only. But it's important that traffic doesn't have to do this. Make sure you have all sub-domains configured. Traffic won't start properly if this is not set up properly. At the initial start, you need a little time until traffic runs and to get all the containers running. It might irritate you, maybe. But the maps, what about that? You can set any map and visit any map you can find openly and publicly. In this marked area it's the quasi-url to the map. For example, we from the ROM-Zitlabour have set this one to the launch event for the SE3. Anyone who goes to your host are on the same map. You can also do your own maps. There's information on the WorkAdventure and other sources. But make sure there's a lot of bugs still and position information isn't interpreted properly. So make sure you keep in mind that you might get frustrated. But on Jitzy, Jitzy is really mighty. You can use any Jitzy-Server you want to use and get reachable for you. I think I don't want to set up my own Jitzy. Jitzy needs a known VM on your own cluster. WorkAdventure doesn't do this. So, if you have a division of these two systems, you don't need your own Jitzy. Jitzy can be configured in different ways and has a lot of parameters. Generally, this might need a completely own talk, but I won't do this here. I spend a lot of time in monitoring and in logging. I don't want to focus on docker commands. I'm a real admin in this case and traffic also annoys me. It's kind of difficult to get it out of the system. I might take a little bit of time for this. Thank you for your attention and you're always welcome to ask me questions. Yeah, definitely. Thank you for the talk. There's always a little work behind this which is not seen in this introduction talk. As soon as we have our questions, people from the stream write your questions in the chat. How many people did you show WorkAdventure and how many people did you help? I think about four or something. I talk to four people for a longer time and help them debug things and do things. It's open for questions and feedback and also thankful for this. So I want more people to use this. What's the most frequent question you get? Why does the container not start? This is basically the summary of it. Sometimes it's a little frustrating to get proper error messages from the docker. For example traffic and the front end is a little buggy sometimes. These are the containers that are a little bitchy. Maybe this might work a little better in the future to get all this information to the people to make finding errors easier. Well, there's actually a few questions from the stream here. What kind of spec should the server have with how big of a amount of people? So I tried it with 120 people and I had the second smallest version on Hetsna. Barely needs storage. I think it had 10 or 20 Gigabits. The images are a little bigger. It's a Node.js container. In the end you have 500 MB or 1 Gigabyte on dependencies. But that's basically it. As far as I can see the usage load isn't that dramatically high. I don't know how it scales with 100, 200 people but I couldn't test it. Future is long. The Ansible. Is it used locally or remote? I'm using it locally. But even some admins use a Windows desktop but it's a little painful. But it was easier for me to put it onto the VM and use there. This is pretty straightforward. Next questions. Question on Jitzi. Is there something I have to take a closer look at when I'm doing this? I personally use my own Jitzi which I set up on a different instance. A lot of different things are running on this machine so I don't want to talk about load and stuff like that. People, for example, who use the public Jitzi from Jitzi This is integrated using a variable in the maps as properties. You can also set up Jitzi rooms using properties and per area you're using It works through layers and certain layers can have a certain Jitzi room and you can say, okay, we have a big meeting room and a big Jitzi which is only there for this so I can say, okay, special property for the Jitzi server and this is a Jitzi room and just go. I had Jitzi issues with authentication if you have authentication and user management set up for this there might be people who have more details inside for my Jitzi instances I said, okay, I don't care I switch off the authentication but there's a possibility to use JWT tokens to restrict the use on WorkAdventure As I see the pad, it's a hot topic many people want to set up a WorkAdventure but we're running out of time, the slot isn't too long just tell us how people can reach you to further discuss all the questions You can reach me using Twitter Furthermore, I'm in the Matrix room of the R2R these are the basic contact options it's also possible to reach me using GitHub for example you can write to me there and I will figure stuff out with all this talk and the Q&A we'll see each other later during this event