| # If you come from bash you might have to change your $PATH. | |
| # export PATH=$HOME/bin:/usr/local/bin:$PATH | |
| export ANDROID_HOME=~/Android/Sdk | |
| export PATH="$PATH:$ANDROID_HOME/tools" | |
| export PATH="$PATH:$ANDROID_HOME/platform-tools" | |
| # Path to your oh-my-zsh installation. | |
| export ZSH="/Users/diegofernandes/.oh-my-zsh" | |
| export PATH="$PATH:/usr/local/bin" |
| // Intercepts all links to Plex in Organizr and redirects to the Plex app on an | |
| // iOS device. Plex for Android apparently does not support such URL schemes, and I | |
| // can't find any alternative Android solution, so this script is iOS-only. | |
| // Add to Organizr Settings > Customize > Appearance > Custom JavaScript. | |
| //////////////////////////////////////////////////////////////////////////////////// | |
| // Credit to https://forums.plex.tv/t/deep-links/205583 for finding Plex deep links | |
| // Use Bowser to check if we're on iOS | |
| var plexiOSCheck = bowser.osname === 'iOS'; |
I am currently working on updating this guide after updating my media server. I have added notes on things I no longer use but may update those sections in the future for users who still use them. As of now, I have everything working with the exception of Ombi and the plugins I no longer use.
This guide has moved to a GitHub repository to enable collaboration and community input via pull-requests.
https://github.com/alexellis/k8s-on-raspbian
Alex
This sets up a publically-available domain that loops back to localhost IP address 127.0.0.1. For example, this address could be localhost.example.com if we controlled the example.com domain. This relies on having a public domain name whose DNS records you can control. We can then generate LetsEncrypt certificates for this domain.
Our HTTP server runs on localhost:80 (default HTTP port). This lets us visit http://localhost.example.com in a web browser and see the server running on localhost:80.
We then run an HTTPS proxy server on localhost:443 (default HTTPS port) that uses the LetsEncrypt certificates we generated for localhost.example.com. Visiting https://localhost.example.com hits the proxy, which returns the correct certificates meaning the browser displays the "Secure" message. The proxy then passes the request through to the HTTP server.
