-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kubernetes Deployment #72
Comments
I don't have much experience with K8S so I won't be able to help. That said, I plan on improving the backend/self-hosting logs. As-is, it's been enough for the Cloud and simple Docker-based self-hosting, but it's indeed a bit limited. If you have any suggestions on that front, I'm happy to hear them. |
That's alright just for the protocol:
Once it is working for me I will share the configuration for your documentation on how to deploy to K8s :) Now besides Kubernetes, I set a subdomain for App to
In Mongodb I could see the entry of the user in Is this the right endpoint for the frontend, because in the Swagger Docu I didn't see such endpoint? |
The REST API (documented here and in the Swagger spec) is used primarly as a public API. The app uses primarly a separate, internal API, with endpoints like the one you've listed. Not exactly sure what could be causing the issue but, if you're using multiple subdomains, be sure to set the |
Thanks it is working now :) I will add a step by step Guide here and then we can close this 🚀 |
How To Deploy Vrite On K8s:It is beneficial to set the right envs and TLS for all Vrite Services. Requirements
Helm CreationThe optimal approach is to generate a Helm Chart using Helm create vrite. This command will establish a Helm framework within your present directory under the release name vrite. The initial chart will serve as the frontend. To complete the setup, you must create three additional services within the vrite chart as SubCharts, namely vrite-api, vrite-collab, and vrite-assets. EnvironmentsYou need the following envs as configMap or Secret: Liveness- and ReadinessProbeFor Vrite-API you can set Liveness- and ReadinessProbe to /swagger.json: livenessProbe:
httpGet:
path: /swagger.json
port: http
scheme: HTTP for Vrite-Assets you need to remove Liveness- and ReadinessProbe, the other ones can be set to path: / |
I’m in the process of setting up Vrite on Kubernetes using a Helm Chart, but I’m facing issues with the Api and Assets—they’re not functioning, and I’m unable to retrieve any logs for debugging purposes. Additionally, when I access the vrite api Pod and execute node index.js, there’s no response or output. Has anyone successfully deployed Vrite on Kubernetes and can offer some guidance?
The text was updated successfully, but these errors were encountered: