search

fmeringdal / nettu-meet

Open source video conferencing system for tutors.
GNU Affero General Public License v3.0
2.28k stars 286 forks source link

Instructions for self-hosting without Docker #26

Open sunrez opened 3 years ago

sunrez commented 3 years ago

Hi,

Would you consider providing some instructions on how to self host this without Docker? For example on a standard Debian install?

fmeringdal commented 3 years ago

Hi,

You need to have a mongo database and redis server running. Then you can run the server by downloading it from here: https://nettu-meet-code-artifacts.s3.eu-west-1.amazonaws.com/server-ubuntu-20.4.zip. Just unzip that and run node dist/index.js and provide the environment variables required.

Joshua-alt commented 3 years ago

how can go long with firebase

un-fuf-a-doo commented 2 years ago

I consider myself to be somewhat skilled when it comes to the installation of a node/react app. I just cannot get your app to run, nothing I do works. I tried your zip archived server, and it won't even start. With some tinkering, I managed to get the server started, but the frontend won't render and errors out completely in the browser.

Running Ubuntu Server 20.04, Node 12 LTS, and the current git tree. All of my infrastructure services are external, but each are definitely reachable. I'm able to connect to each database/service using telnet or a browser for kibana.

Why the need for so many database types? What does having redis and mongo do that mongo alone can't? I still haven't even begun to try and understand why elasticsearch is necessary on top of the others.

Maybe if you created a flowchart of your thought process with the overall design I could figure out what is broke. Current error on the server complains about elasticsearch connectivity. But again I can connect to elastic via telnet to port 9200 from the server host so I don't know why the server backend can't.

Ok done venting...

J

Joshua-alt commented 2 years ago

thanks but with docker is much more easy

Le dim. 5 sept. 2021 à 04:44, Jeff @.***> a écrit :

I consider myself to be somewhat skilled when it comes to the installation of a node/react app. I just cannot get your app to run, nothing I do works. I tried your zip archived server, and it won't even start. With some tinkering, I managed to get the server started, but the frontend won't render and errors out completely in the browser.

Running Ubuntu Server 20.04, Node 12 LTS, and the current git tree. All of my infrastructure services are external, but each are definitely reachable. I'm able to connect to each database/service using telnet or a browser for kibana.

Why the need for so many database types? What does having redis and mongo do that mongo alone can't? I still haven't even begun to try and understand why elasticsearch is necessary on top of the others.

Maybe if you created a flowchart of your thought process with the overall design I could figure out what is broke. Current error on the server complains about elasticsearch connectivity. But again I can connect to elastic via telnet to port 9200 from the server host so I don't know why the server backend can't.

Ok done venting...

J

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/fmeringdal/nettu-meet/issues/26#issuecomment-913075175, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANQD4P5RUKHQ6BOTHYPLRN3UALKPXANCNFSM47YRS4JQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

un-fuf-a-doo commented 2 years ago

My infrastructure services are running in docker, just not on the localhost server. You can't possibly expect someone to host everything on the same server? That simply is not secure and not how things are done today. Separating the frontend, server, and infrastructure services is the correct way to deploy, but this codebase doesn't work that way it seems.