Open abbi-gaurav opened 3 years ago
Hey @abbi-gaurav ,
There are 3 important containers:
There is already a PR with Helm charts here: https://github.com/thecodingmachine/workadventure/pull/652 Maybe you could take a look at it? I'm sure this should help.
Thanks, I will check it out
Thanks @moufmouf , I followed the helm PR and deployed on Kubernetes. However, I see some weird behavior
The TMC frame stays on top. Is there a way to hide it?
The app does not seem to respond.
I see the errors, not sure if they are related
I do not see any error logs in the server-side apps.
Any configurations, that I can possibly change. I am using the following docker images
thecodingmachine/workadventure-back:v1.1.0 thecodingmachine/workadventure-front:v1.1.0 thecodingmachine/workadventure-maps:v1.1.0 thecodingmachine/workadventure-pusher:v1.1.0 thecodingmachine/workadventure-uploader:v1.1.0
Can you potentially publish your manifests your using?? Would help others to get this up on k8s as well!
@abbi-gaurav could you explain your steps, please? I'm also interested in a similar deploy. @Kampe do you have more details? Thanks!
Hi, I am trying to set up the working adventure on a k8s cluster. I have created k8s deployments and services for pusher, back and front. Pusher and front have been been exposed via an Istio ingress (a reverse proxy).
When accessing the UI, I see HTTP 500 errors for API_URL in front is/pusher/map?organizationSlug=tcm&worldSlug=workadventure&roomSlug=corridor
https://working-adventures.<domain>/pusher
which maps to pusher deployment and service. https://working-adventures.Who is supposed to serve it? Pusher or some other application?
In the pusher, I see the following logs
As I understand, for the open source version, admin API URL is not required. Is there a flag to disable it?