https://github.com/tetele/onju-voice-satellite
This Gist will no longer be maintained, please check out the new location for the config.
Ever since voice satellites were introduced to Home Assistant, people wanted to use good microphones and speakers for this purpose, but not many were really available.
| # Edit and rename this file and then place it in /etc/wyzecam-to-rtmp | |
| WYZE_EMAIL="joeblow@example.com" | |
| WYZE_PASSWORD="wyzepasshere" | |
| WYZE_CAMERA_NAME="Doorbell" | |
| RTMP_URL="rtmp://127.0.0.1/live/doorbell" |
As of January 2020, all apps running on macOs 10.15 Catalina are required to be notarized. For Unity games distributed outside the Mac App Store, such as with Steam, the notarization process is done post build using a series of Xcode command line tools.
| """ | |
| Copyright 2019 Jason Hu <awaregit at gmail.com> | |
| Licensed under the Apache License, Version 2.0 (the "License"); | |
| you may not use this file except in compliance with the License. | |
| You may obtain a copy of the License at | |
| http://www.apache.org/licenses/LICENSE-2.0 | |
| Unless required by applicable law or agreed to in writing, software |
| # NGiNX reverse proxy configuration for Jellyfin | |
| # | |
| # Use this configuration on NGiNX running on the same server as your Jellyfin instance. Replace the values as needed. | |
| # LetsEncrypt is enabled and configured using `certbot`: install it via apt on Debian (`sudo apt install certbot`) or | |
| # your package manager of choice. To start, make only the first section (port 80) active, then once that configuration | |
| # is active, run Certbot for the first time to request your cert. Then, add the second section (port 443) and reload. | |
| # With this config left in place, Certbot's automatic renewal will work and automatically replace the cert and | |
| # reload NGiNX as needed, without interrupting your Jellyfin instance. | |
| # | |
| # Certbot request command: |
| POWER TOGGLE = JgDMAFUfDRANEQwfDR4rHg0QDRANEA0QDRANEA4QDRANEA0QGxANEA0QDh4cEA0QDR4cHg4QDRANEA0QDRAbEA0fDRANAAjTVSANEA0QDR4NHyofDg8NEA0QDRANEA0QDRANEA0QDRAcEA0QDRANHhwQDRANHx4cDRANEA0QDRANERsQDR4ODw4ACNNYHA0QDRANHw0eKh8NEA0QDREMEQwRDBANEA4QDRANEBsQDRANEA0fHBANEA0eHB4NEA4QDRANEA0QHA8NHw0QDQANBQAAAAAAAAAAAAAAAA== | |
| POWER ON = JgDGAFcdEA4PDg8cDxwtHBAODw4PDg8ODw4PDg8ODw4PDg8OHg4PDg8ODw4PDg8ODw4PHB4cEA4PDg8OHhweHB4cEAAI0FgdDw4PDg8dDxwtHA8ODw4PDg8ODw4PDg8OEA0QDg8OHQ4PDg8OEA0QDRAODw4PHB4cDw4QDRAOHRweHB4dDwAI0VcdEA0QDg8cDxwtHBANEA4PDg8ODw4PDg8ODw4PDg8OHg4PDg8ODw4PDg8ODw4PHB4cEA4PDg8OHhweHB4cEAANBQAA | |
| POWER OFF = JgDAAFceDRAPDg8cDx0sHBAODw4PDg8ODw4PDg8ODw4PDg8OHg4PDg0QDxweDg8ODx0dHQ8ODw4PDh0dHB4PDhwACOJXHQ4PDw4PHQ8cLRwQDQ4PDg8OEA4PDg8ODw4PDw4ODx0PDg8ODw4dHg4ODw4dHh0ODw4PDg8cHh0dDg8dAAjgWBwQDg8ODxwQHCwcEA4PDg8ODw4PDg8ODw4PDg8ODw4eDg8ODw4PHB4ODw4QHB4cDw4PDg8OHhweHBAOHQANBQAAAAAAAAAA | |
| PLAY = JgDGAFgcEA4PDg8cEBwsHBAODw4PDg8ODw4PDg8ODw4PDhANHg4PDg8ODxwfDRANEBweHA8ODw4QDRANHhweDg8dDwAI0VcdDw4PDhAcDxwtHA8OEA0QDg8ODw4PDg8ODw4PD |
With Windows Containers, as with any application, you will need to consider your logging strategy. In the containers world it is generally accepted to log to STDOUT/STDERR (standard out and standard error). As you scale up your services you will need to aggregate and store these logs for analysis and debugging later on. There exist many back end systems to aggregate logs and help with analysis, in Azure you have Log Analytics and Application Insights.
There are two general strategies for configuring your containers to send logs to a backend logging system containers:
| # Use this script to test that your Telegram bot works. | |
| # | |
| # Install the dependency | |
| # | |
| # $ gem install telegram_bot | |
| # | |
| # Run the bot | |
| # | |
| # $ ruby bot.rb | |
| # |
