Ben Porter FreedomBen

Overview: running crc on a remote server

This document shows how to deploy an OpenShift instance on a server using CodeReady Containers (crc) that can be accessed remotely from one or more client machines (sometimes called a "headless" instance). This provides a low-cost test and development platform that can be shared by developers. Deploying this way also allows a user to create an instance that uses more cpu and memory resources than may be available on his or her laptop.

While there are benefits to this type of deployment, please note that the primary use case for crc is to deploy a local OpenShift instance on a workstation or laptop and access it directly from the same machine. The headless setup is configured completely outside of crc itself, and supporting a headless setup is beyond the mission of the crc development team. Please do not ask for changes to crc to support this type of deployment, it will only cost the team time as they politely decline :)

The instructions here were tested with F

Latest Update 2021-03-06 : New image showing the new "Services" in Home Assistant and got some tips from the comments below.

Credits and thanks: Home Assistant Forum users & Github users: @ocso, @wiphye, @teachingbirds, @tboyce1, @simbesh, @JeffLIrion @ff12 @rebmemer @siaox @DiederikvandenB @Thebuz @clapbr @Finsterclown

Start apps on your android device (in the examples below, my Nvidia Shield TV) from Home Assistant

Starts Youtube App

entity_id: media_player.shield
command: >-

Sessions

Code	Title	Duration	Link
Keynote	Andy Jassy Keynote Announcement Recap	0:01	https://www.youtube.com/watch?v=TZCxKAM2GtQ
Keynote	AWS re:Invent 2016 Keynote: Andy Jassy	2:22	https://www.youtube.com/watch?v=8RrbUyw9uSg
Keynote	AWS re:Invent 2016 Keynote: Werner Vogels	2:16	https://www.youtube.com/watch?v=ZDScBNahsL4
Keynote	[Tuesday Night Live with Jame

	# ~/src/non-oss-container/build.sh

	#!/bin/bash

	set -euo pipefail

	mkdir -p ~/non-oss-root/

	podman image rm --force localhost/non-oss \|\| :

	#!/bin/bash -xe
	ORGANIZATION='community-operators'
	OPERATOR_NAME='db-operator'
	# CATALOG_IMAGE='registry-proxy.engineering.redhat.com/rh-osbs/iib:12906'
	CATALOG_IMAGE='quay.io/redhat-developer/sample-db-operators-olm:v1'
	MIRROR_REGISTRY='ec2-52-15-216-90.us-east-2.compute.amazonaws.com:5000/'$ORGANIZATION/$OPERATOR_NAME:v1
	USER_NAME='dummy'
	PASSWORD='dummy'

	# docker login -u $USER_NAME -p $PASSWORD $MIRROR_REGISTRY

	{
	"key_events": {
	"key_unknown": "adb shell input keyevent 0",
	"key_soft_left": "adb shell input keyevent 1",
	"key_soft_right": "adb shell input keyevent 2",
	"key_home": "adb shell input keyevent 3",
	"key_back": "adb shell input keyevent 4",
	"key_call": "adb shell input keyevent 5",
	"key_endcall": "adb shell input keyevent 6",
	"key_0": "adb shell input keyevent 7",

	#!/usr/bin/env bash

	# Gets all tags for a given docker image.

	# Examples:

	# retrieve all tags for a single library
	# docker-tags "library/redis" \| jq --raw-output '.[]'

	# retrieve all tags for multiple libraries

	# Use envFrom to load Secrets and ConfigMaps into environment variables

	apiVersion: apps/v1beta2
	kind: Deployment
	metadata:
	name: mans-not-hot
	labels:
	app: mans-not-hot
	spec:
	replicas: 1

	default['sshd']['sshd_config']['AuthenticationMethods'] = 'publickey,keyboard-interactive:pam'
	default['sshd']['sshd_config']['ChallengeResponseAuthentication'] = 'yes'
	default['sshd']['sshd_config']['PasswordAuthentication'] = 'no'

	# How to run Ecto migrations from IEx console... Examples

	# preliminaries assumed in the following code, change to fit your environment:
	alias YourAppName.Repo
	your_app_name_as_atom = :mpnetwork
	downto_version = 20170724182558

	# Down:
	Ecto.Migrator.run(Repo, "priv/repo/migrations/", :down, [to: downto_version])