Skip to content
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

Instructions for self-hosting without Docker #26

Open
sunrez opened this issue Jul 3, 2021 · 5 comments
Open

Instructions for self-hosting without Docker #26

sunrez opened this issue Jul 3, 2021 · 5 comments

Comments

@sunrez
Copy link

sunrez commented Jul 3, 2021

Hi,

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

@fmeringdal
Copy link
Owner

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
Copy link

how can go long with firebase

@un-fuf-a-doo
Copy link

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
Copy link

Joshua-alt commented Sep 5, 2021 via email

@un-fuf-a-doo
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants