Basic setup for HomeAssistant using zwave-js-ui for z-wave, and ser2net to host the z-wave usb stick on TCP port. We use ser2net, because USB device passthru doesn't work on Docker Mac, Docker Windows, or Swarm-mode (even on Linux).
This system is running on a Raspberry Pi 3 B+, however I also had it running on a Mac (Mojave) using 'nix' package manager to install ser2net.
Some paths and device names are specific to my setup.
| #!/bin/bash | |
| # Launches two stripe-cli docker containers, each in its own 'screen' session, | |
| # to test stripe webhook events against a local http server. | |
| # | |
| # * Launches one container for the listener/forwarder. | |
| # * Launches one container to trigger the test webhook event. | |
| # | |
| # NOTE: The stripe-cli 'trigger' function will create a lot of data in your | |
| # stripe account's test environment. The only way to remove that data is manual one-by-one |
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <!-- | |
| This is an example of a reusable html tabs vuejs-3 component. | |
| You can set this up once in your project and create as many | |
| tabbed interfaces as you like, with no extra code. | |
| This example was taken from https://github.com/mattmaribojoc/learn-vue-tab |
| # frozen_string_literal: true | |
| # This gemspec currently describes a gem hosted on Github as a Gist only. | |
| # See https://bundler.io/guides/git.html | |
| require_relative "json_rpc_object_version.rb" | |
| Gem::Specification.new do |spec| | |
| spec.name = "json_rpc_object" | |
| spec.version = JsonRpcObject::VERSION |
| source "https://rubygems.org" | |
| gem 'json_rpc_object', gist:'5b128c655e79e1b4e0e10c27a5098177' | |
| #gem 'connection_pool' | |
| #gem 'json_rpc_object', path:'../JsonRpcRuby' | |
| # Declare your gem's dependencies in foo.gemspec. | |
| # Bundler will treat runtime dependencies like base dependencies, and | |
| # development dependencies will be added by default to the :development group. | |
| gemspec |
| ### Converts Reaper data file (.rpp) to YAML, using Awk. | |
| ### All scalar values will be enclosed in single quotes. | |
| ### | |
| ### Usage: (with standard input) cat <reaper-data-file.rpp> | <this-script-file> | |
| ### (with filename as first arg) <this-script-file> <reaper-data-file.rpp> | |
| ### | |
| ### Returns: formatted YAML document | |
| ### | |
| ### Example usage with yq (shell-based yaml parser): | |
| ### |
This document was written for the ginjo-omniauth-slack ruby gem. It attempts to clarify the OAuth2 authorization cycle and how that cycle is implemented in your appliation with the ginjo-omniauth-slack gem.
The OAuth2 cycle is a three-way dance between the user's browser, the OAuth2 provider (Slack API), and the application server (your Slack App). It should work this way for any OAuth2 provider, including Slack.
https://slack.com/oauth/authorize, passing the application's client-id, requested-scopes, and optionally state, team-id, and redirect-uri. Slack then runs the user through the authorization dialogs.
| ### This is an OmniAuth::AuthHash object from the ginjo fork of omniauth-slack. | |
| ### This AuthHash represents a workspace token with a number of identity and non-identity scopes. | |
| --- !ruby/hash:OmniAuth::AuthHash | |
| provider: slack | |
| uid: U0BCC482X-T0BCJPFAM | |
| info: !ruby/hash:OmniAuth::AuthHash::InfoHash | |
| name: Bill | |
| email: xxx@mac.com | |
| user_id: U0BCC482X |
| --- !ruby/hash:OmniAuth::AuthHash | |
| provider: slack | |
| uid: U281GAVT5-T0BCJPFAM | |
| info: !ruby/hash:OmniAuth::AuthHash::InfoHash | |
| name: Bill Richards | |
| email: myemail@gmail.com | |
| user_id: U281GAVT5 | |
| team_name: WbrSandbox | |
| team_id: T0BCJPFAM | |
| image: |
| wbr$ terraform destroy | |
| ... | |
| module.worker.aws_instance.node: Destroying... (ID: i-007df99effb41b99c) | |
| module.worker.aws_instance.node: Provisioning with 'remote-exec'... | |
| module.worker.aws_instance.node (remote-exec): Connecting to remote host via SSH... | |
| module.worker.aws_instance.node (remote-exec): Host: 54.218.80.101 | |
| module.worker.aws_instance.node (remote-exec): User: admin | |
| module.worker.aws_instance.node (remote-exec): Password: false |