Updated server installer

lovefmhits commented 4 years ago

good evening here I just found your site which is great for broadcasting but I cannot find any info on installation and if it is possible to install on a vps then meric tell me if it is possible or I can find the commands for liniux thank you very much for your little answer john from france

radiorob commented 4 years ago

Hi John. Check out the README file with resource links and ob.installer.sh

lovefmhits commented 4 years ago

good evening thank you for your answer so just that I do not see this link don you talk to me if possible send it to me thank you very much

lovefmhits commented 4 years ago

hello rob so I found ob.installer.sh but inpossible to install on the vps I am an Ubuntu system here then tell me if it is normal or not I thank you

Le mar. 3 nov. 2020 à 14:23, Rob Hopkins notifications@github.com a écrit :

Hi John. Check out the README file with resource links and ob.installer.sh

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/openbroadcaster/observer/issues/15#issuecomment-721328014, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEU55Z6LRKUP4ZCECCFNCODSOBKCPANCNFSM4TJENGUQ .

stratos-max commented 3 years ago

good evening here I just found your site which is great for broadcasting but I cannot find any info on installation and if it is possible to install on a vps then meric tell me if it is possible or I can find the commands for liniux thank you very much for your little answer john from france

Hi, I can't install the server on a ubuntu 20.04 VM. Could you help me?

Sturmey66 commented 3 years ago

It looks like there is an issue with the ob.installer.sh file and Ubuntu 20.04 something in the if section is failing, then it looks like their is an option that throws "Illegal option -s" when it's in the database creation part.

looks like its part of this read -sp "xxxxxxxxxx

Also there appears to be an issue with the if else portion when it gets to the database creation part. I'm not sure what's happening yet. It will have to wait until next week. possibly something with the variable name and how it's accessed.

Sturmey66 commented 3 years ago

Something in line #47 is causing the error.

if [[ $USEDBRT == "" ]]; then

wcarman1 commented 3 years ago

Run the command as bash ob.installer.sh for some reason it doesn't work if you just run ./ob.installer.sh. At least on Debian 10 it was that way. I assume Ubuntu would be the same way.

Sturmey66 commented 3 years ago

bash ob.installer.sh does seem to work, however after completing the script and attempting to log into the system, I just get an index page, so something isn't quite right on my end. More investigation is needed.

wcarman1 commented 3 years ago

I thought for sure that would fix it. I had to run it as bash when I set it up on my test VM and on the actual server. As for the index, Did you disable the default page?a2dissite 000-default copy the ob.apache.conf file to the /etc/apache/sites-available/ directory. Then a2ensite ob.apache.conf Followed by a systemctl reload apache2. It took me forever to get it all working. I had to completely delete everything including the database a couple times and eventually I got it.

Also if the database part of the script is giving you trouble, either purge Mariadb completely and start over or log into it and drop the openbroadcaster db. If even part of it has been created it will fail, I noticed. Also I found out after my first run at the install that you have to initialize mariadb by setting a root password and removing the test db.

Lastly, I believe you can remove the s switch from all instances of read -sp ... that will just make your passwords display in plain text in the terminal. Debian 10 didn’t like the s switch until I ran it as bash ob.installer.sh

cchapman900 commented 3 years ago

I think there is an issue with the install script still trying to find the tools/password_hash.php file, although that file seems to have been deleted in the "update to version 5.1" commit. I added that file back in, and everything seems to have gone more smoothly.

The file contents are:

<?php

if(php_sapi_name()!='cli') die('cli only');

if(empty($argv[1]) || empty($argv[2])) die();

// argv[1] = password
// argv[2] = salt

echo password_hash($argv[1].$argv[2],PASSWORD_DEFAULT);

Neepawa commented 3 years ago

Run the command as bash ob.installer.sh for some reason it doesn't work if you just run ./ob.installer.sh. At least on Debian 10 it was that way. I assume Ubuntu would be the same way.

Doing chmod +x ob.installer.sh and running ./ob.installer.sh will not work. The shebang line on the script is #!/bin/sh, which is a stripped down version of the shell that's not compatible with bash. You first need to alter the line to read #!/bin/bash, then you can run it as ./ob.installer.sh. However, that won't fix the other bugs in the script.

Neepawa commented 3 years ago

Something in line #47 is causing the error.

if [[ $USEDBRT == "" ]]; then

You're correct there. If USEDBRT is not set, the shell will expand the line to

if [[ == "" ]]; then

and subsequenty display an error. The correct syntax for this test is either

if [[ "$USEDBRT" == '' ]]; then

or more concisely,

if [[ ! "$USEDBRT" ]]; then

Overall, the installation script needs some TLC from an experienced shell scripter (like me.) However, I'm not seeing much interaction from radiorb here. I'd like to see some input from him before I do a re-write.

radiorob commented 3 years ago

@Neepawa Thanks for the comments and observations. I do receive comments from advanced users being able to do the setup, but an installer will make less work. We have a much more complex and current enterprise installer that our @openbroadcaster/ob-core-devs are syncing the server parts to ob.installer.sh to make an easier setup experience. We will release this with some updated server code that has been through testing as well and look forward to your feedback.

gitcoinbot commented 3 years ago

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

This issue now has a funding of 100.0 USD (99.96 USD @ $1.0/USD) attached to it as part of the OpenBroadcaster fund.

If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
- Want to chip in? Add your own contribution here.
- Questions? Checkout Gitcoin Help or the Gitcoin's Discord
- $7,106,539.41 more funded OSS Work available on the Gitcoin Issue Explorer

gitcoinbot commented 3 years ago

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Workers have applied to start work.

These users each claimed they can complete the work by 2 months from now. Please review their action plans below:

1) rush-skills has applied to start work _(Funders only: approve worker | reject worker)_.

I will fix the bash installer script ob.installer.sh to make it compatible with Ubuntu 20.04 2) vincentthedev has applied to start work _(Funders only: approve worker | reject worker)_.

Provide code changes required to improve the installer, including Debian/Ubuntu/raspberry pi support.

Learn more on the Gitcoin Issue Details page.

rmens commented 3 years ago

Was eager to try this software out after hearing about it on TWIRT. But the installation was kinda hard.

I updated some dependencies in https://github.com/openbroadcaster/observer/pull/18 so at least the basics get installed, but the script seems to need a lot more work.

gitcoinbot commented 2 years ago

@vincentthedev Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

[x] reminder (3 days)
[ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

gitcoinbot commented 2 years ago

@vincentthedev Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

[x] reminder (3 days)
[ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

gitcoinbot commented 2 years ago

@vincentthedev Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

[x] reminder (3 days)
[ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

gitcoinbot commented 2 years ago

@vincentthedev Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

[x] reminder (3 days)
[ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

gitcoinbot commented 2 years ago

@vincentthedev Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

[x] reminder (3 days)
[ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

gitcoinbot commented 2 years ago

@vincentthedev Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

[x] reminder (3 days)
[ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

rmens commented 2 years ago

I keep getting e-mail spam from Gitcoin after commenting on this issue. Can an admin snooze them? Thanks!

radiorob commented 2 years ago

Excuse while I figure out how to stop these from polluting inbox. That is annoying for all and can't see a way to snooze, will have this closed ASAP and that will get rid of the bot. Upside we have work on new installer and new code, thanks @rmens for the dependencies shortcut.

gitcoinbot commented 2 years ago

@vincentthedev Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

[x] reminder (3 days)
[ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

vincentthedev commented 2 years ago

New installer is currently WIP. Installer should work now for Nginx.

rmens commented 2 years ago

It just doesn't stop 🥲

radiorob commented 2 years ago

I have a support ticket in about this and you are right annoying and broken. Glad I didn't add this to all issues :-) Will get this closed very soon. We have the installer script in beta and out for testing. If there is anyone on this thread that would like to get beta, message me off list. Also heads up, when the installer is committed, closed, resolved, paid out that should get rid of the notifications. If they continue (like spam) I'll delete this entire issue, so this issue might just disappear without notice. Excuse again.

On 2021-11-20 3:57 p.m., Raymon Mens wrote:

It just doesn't stop 🥲

—

radiorob commented 2 years ago

Almost ready to close this issue. I have been trying to snooze this bot, keeps coming back. Am I missing something to mute this bot? Could really use some expertise if there is anyone that has some insight.

Response from Gitcoin support (option to snooze broken)

The solution given is to mute your Bot notifications. You can do so on Github itself, so if you go the Github issue where gitcoinbot is commenting on, there should be an option to snooze. Alternatively, you can also do it from the admin or contact Github directly.

Screenshot at 2021-11-25 10-23-26

radiorob commented 2 years ago

Hello. Thanks for patience and assistance with new installer. I can report multiple independent users having success getting into the server dashboard with this method. Call out to @vincentthedev for completing this project. https://github.com/openbroadcaster/observer/blob/main/ob.installer.sh

openbroadcaster / observer

Updated server installer #15