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

installing instructions not clear at all #183

Closed
nikto1 opened this issue Feb 13, 2024 · 3 comments
Closed

installing instructions not clear at all #183

nikto1 opened this issue Feb 13, 2024 · 3 comments

Comments

@nikto1
Copy link

nikto1 commented Feb 13, 2024

Hi there,

maybe for you guys that are working on the project the installation process is crystal clear but for me - and i think for other people too - not at all.
I have enough resourses to run also other stuff there, not just galene. Based on this so is it possible to run galene with other stuff installed. From what i've understand not at all.

  1. Then connect to https://localhost:8443 and choose “test”. --> you're supposing galene is installed locally and there is already an SSL certificate installed? E.g. in my case i've installed galene for a user on an online server in a subdomain and when i try to access https://subdomain.example.com:8443 it gives me a connection reset error although i have a ssl certificate for the domain + subdomain. Port 8443 is obviously open.
  2. mkdir groups vi groups/name.json --> where should the folder "groups" be made? Inside the root directory or in the folder where galene is installed? If so, wouldn't it be better to make an empty folder/ file named "groups/name.json" by default? Otherwise you're supposing everyone has access to the whole server?
    Note: if i start galene from e.g. "home/users/server_user/www/galene" i got a "Group file ./groups/: lstat ./groups/: no such file or directory" error but if i start galene from within the installation (./galene) the folder "groups" is found.
  3. ./galene & --> please clarify, what does this do, what happens and which user/ where should it be executed? Should it be executed as "root"? If so, i suppose the whole installation goes inside the "/" folder. If the answer is positive, how to deploy the server for a specific user on a specific domain?
  4. Deploy to your server --> Not clear at all. E.g. where's the "data/ice-servers.json" folder/ file, how to stop galene/ build in turn server, what are the possible configuration options, ecc.? Maybe put a default configuration somewhere with some comments so people know how to configure it.
    It would also be good to give some advices, e.g. if you have HSTS enabled, a self-signed SSL will interrupt the connection so a valid certificate is required. As letsencrypt renews certifcates each 3 months the whole copy/paste process of the *.pem files should be executed with a cron job or stuff like that.
  5. Connectivity issues and ICE Servers --> same as 4

Would be great to make a more comprehensive guide so i could try it out.

Thanks a lot in advance

@jech
Copy link
Owner

jech commented Feb 16, 2024

maybe for you guys that are working on the project the installation process is crystal clear but for me - and i think for other people too - not at all.

Thank you for your feedback. Installing from source is always more involved than installing from a distribution. Please consider using Yunohost, which provides an automated installation procedure for Galene.

Should you insist on installing from source, please consider subscribing to the galene@lists.galene.org mailing list, which is more suitable for support requests than this issue tracker.

@jech jech closed this as completed Feb 16, 2024
@dashohoxha
Copy link

@nikto1
These scripts try to automate the installation of Galene:
https://gitlab.com/docker-scripts/galene
I use them for myself. Can you have a look and see if they help you somehow?

@nikto1
Copy link
Author

nikto1 commented Feb 17, 2024

I got galene already running but had to read the sourcecode in order to do so. Although i have no idea about GO i found the flags and other stuff so i tought it was a good idea to document the whole stuff better from 0. When i have some time and understand the code completly (coming from C, phyton, php) i'll write a complete documentation and share it on github 'cause i think i'm not the only one who had difficolties understanding the docs.

@dashohoxha thanks a lot, will take a look at them and add them to the docs for others if i find they're useful.

@jech thanks, i'll consider subscribing to the list.

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

3 participants