Self-hosted version tutorial (w/o Docker) #43
Comments
|
Thanks. I'am trying to install this also locally. Apache, PHP, mysql and Composer is installed. I just downloaded the zip from github and put the web folder in /var/www/xxx/. |
|
Hey @glsf91, I didn't manage to make the entire setup work (and I'll reply with the details of my current issue as soon as possible), but I stumbled upon that error and got it working by first issuing: Afterwards you can resume with artisan. |
|
@nonsintetic @ispeaknousa At google account linking I have to add a url like /gbrigde/gapi/auth. What to do? Also something else: |
|
The link you need depends on how you setup your webserver. It's basically /gapi/auth . If the address you use to login is yourdomain.com/login, then the url you want for google is yourdomain.com/gapi/auth. If it is yourdomain.com/gbridge, then you'd use yourdomain.com/gbridge/gapi/auth. Make sure you use https for the url and it actually works. You can access the url before entering it into google, if it gives you something (not 404, page not found etc.) it should be ok. |
|
@nonsintetic But how do I get rid off index.php in de url ? I use apache and in my virtual host there is: |
|
You need to enable the 'mod_rewrite' php module. That will rewrite the URLs to not have index.php. The website has a .htaccess file that will handle all that part |
|
Thanks. rewrite was enable but I had to add AllowOverride All |
|
It is working now. I did a lot of things to make it work. |
|
The vendor folder is usually created by |
|
Ok, here's my issue: whenever I try to change the user password, the next error is being raised by laravel: Is anyone else experiencing the same behavior? Software versions:
|
|
That password error only appears in PHP 7.3+ where they changed the PHP PCRE engine version. The new version is incompatible in some cases. The problem is most likely related to a hyphen not being escaped. You can either modify the pattern used by preg_match in that file, or use a lower php version. Should be a different issue since it's not related to self-hosted or not. |
No issue here. I use PHP 7.2 |
|
Thank you both! I've left it running with 7.3 (manually changed the password in the database) and I'll open a separate ticket for it. Another thing related to self-hosting: the |
|
Do you think it can run on a raspberry pi model b? Would it be possible to download an image with everything setup or does it need to be installed separately? |
That's what I run it on, it barely uses any resources, you'd probably be able to run it on a Pi Zero too. The SSL certificate and domain setup would have to be automated somehow since it's different on each install. |
|
Is this solution still works? I see the messages are 1 year old and I want to install it for myself. I know gbridge is not developed anymore. |
|
Have not used it since then. Can't say for sure. |
|
I'am still using it. |
|
I setuped the code and its working for me. I have an issue can you please help me out with google auth with response_type as code instead token Google stopped Oauth implicit method https://gbridge.kappelt.net/gapi/auth? /gapi/auth? Thank You |
I've managed to get the whole system up and running without Docker, so here's more of an outline on what you need to do. The whole thing works fine on a Raspberry Pi 4, should work on any modern Linux system, all the things used are very basic programs.
Follow the gBridge tutorial up to the 'docker' parts and then follow the steps below. I'll try to do a more detailed tutorial with commands, but this is for people having trouble with the recent server outage. There's two parts you need to get running for this to work: an admin website which handles creating accounts/devices and the oAuth part required by Google, and two nodejs apps that handle the actual bridging of commands from the Homekit API to the MQTT server. The admin app is just a normal PHP website built in Laravel. Here's some basic steps you have to follow:
First you need to setup a basic webserver WITH PHP, MYSQL AND SSL (apache/nginx + mariadb/mysql + letsencrypt's certbot) to serve the Laravel website (in the /web folder) just like any other website. Laravel's public stuff is in the /web/public folder, so you either need to add a .htaccess in the /web root to rewrite everything to /public, or you can setup the directory in your webserver's config (in Apache it's a VirtualHost directive). You also need some sort of domain name, a dynamic DNS if you have a dynamic ip, or just a classic domain if you're on a static IP. You'll also need some PHP extensions installed: php-xml, php-mysql.
(If you already have a webserver with PHP up and running, then you're absolutely gold. Just copy the /web folder and do a redirect. Make sure you have a domain name and SSL certificate.)
All the settings for the Laravel app are in the
.env.examplefile, which you have to rename to.envfor it to work. The actual values you can copy from the docker generator mentioned in the gBridge tutorial (the part about docker). You'll have to run your database locally, so the link to it would be 'localhost', same for any other services. You also have to skip the whole Proxy setup in Apache/Nginx that is mentioned in the main tutorial. This will be a run of the mill, basic PHP+MYSQL setup, just like for Wordpress or any other website.(For this whole webserver part you can google individual tutorials for each piece 'php mysql ssl server setup raspberry pi' for example, or 'apache php install debian', 'certbot install debian' etc. Since it's Laravel, you can also find tutorials on how to install a Laravel app/website on a server, it should be pretty straightforward.)
Next step is to navigate to the root folder of the website in SSH or console (not browser) and run the 'artisan' script using php's commandline tool. The command is
php artisan migrate. 'artisan' is part of the Laravel (the framework used to build this admin website). It's a php script that can do various tasks in Laravel, like importing database entries. This will create all the necessary database tables for the website. That might give you errors about various PHP extensions missing on your machine, just install and enable those until it all works (usually it's justapt-get install <extension name>).You'll know the whole website part is correct when you can access the website on your own server and log in (artisan will ask you for an e-mail, it will create a first account and setup a password for you). Once logged in everything on the web side is exactly like the hosted solution, you can make multiple accounts, add devices for each of them, setup mqtt topics etc.
During device creation you'll get some errors, this is because you're still missing 2 nodejs apps. (these are not required for linking your account, but it's better to just install them too before linking, less errors). These two apps handle the sending and receiving of the actual actions, in essence these do all the hard work magic that makes the system work.
To run these you need to first install nodejs, if you have node-red you already have it (nodered is a nodejs app). You also need Redis, a caching system, install that too. After all this you need to run
npm installin each of the 'redis-worker' and 'rs-worker' folders. This will install all the required nodejs libraries for each app. You then need to add the Redis server's IP to each 'config.sample.js' file in these folders and rename them to 'config.js'. To run a node app as a test donode index.jsand the app should start, it should output some text and tell you it's connected. You only need the 'redis-worker' to actually control devices, so just run that in the console for testing at first. The rs-worker will handle sending the state of the devices back to google so you see the device state there too, it's not 100% required to just turn stuff on/off etc. You can create systemd services to keep these running in the background on most Linux distros that have systemd (ubuntu, debian, rasbian etc.). Google 'nodejs systemd' and you'll find tutorials, it's just making a text file and running some commands, then you can run them on startup just like any other service (there's also pm2 as a way to turn nodejs apps into services, but that's way more involved, it's a separate app).If you managed to get all that crap working, it should work just like the hosted solution. Whatever issues you encounter, just google search and hope for the best. It is 100% running with the code here on a Raspberry Pi 4, I've done it today, i can confirm it. All the required pieces should be available as 'apt-get' packages, easy to install on any common linux system.
The text was updated successfully, but these errors were encountered: