Required stack
필요 기술
PHPWebsite DesignGraphic DesignCloud ComputingHTMLWeb HostingWeb DevelopmentAPI IntegrationJitsi MeetLinuxNGINXDockerServer ManagementDNSSSL/TLSAuthentication (SSO/OAuth/JWT)DevOps
Project brief
프로젝트 내용
I want to run Jitsi Meet under my own domain instead of relying on the public meet.jit.si service. My site is currently on a shared-hosting plan, so the first step is verifying whether we can keep everything there or whether we should spin up a small external node and simply route traffic from the main domain—please advise.
Key requirements
• A fresh Jitsi Meet installation reachable at a sub-domain of my choice.
• Recording enabled from day one (Jibri or an equivalent approach).
• Room access tied to the login/registration system that already powers my site, so a visitor who is signed-in can create or join meetings without re-entering credentials.
Once the instance is running I need basic branding tweaks (logo and colour palette) and a short set of instructions showing me how to create rooms, start/stop recordings and manage updates.
If you have completed similar self-hosted Jitsi deployments, especially on resource-constrained environments, I would love to see them.
Key requirements
• A fresh Jitsi Meet installation reachable at a sub-domain of my choice.
• Recording enabled from day one (Jibri or an equivalent approach).
• Room access tied to the login/registration system that already powers my site, so a visitor who is signed-in can create or join meetings without re-entering credentials.
Once the instance is running I need basic branding tweaks (logo and colour palette) and a short set of instructions showing me how to create rooms, start/stop recordings and manage updates.
If you have completed similar self-hosted Jitsi deployments, especially on resource-constrained environments, I would love to see them.