Dan Reiland dmreiland

Proxmox - SPICE client setup for MacOS

Install a working (and compiled) version of virt-viewer. You may view the homebrew package's upstream source on GitHub.
```
brew tap jeffreywildman/homebrew-virt-manager
brew install virt-viewer
```
Once that's installed should be able make a call remote-viewer with a pve-spice.vv file downloaded from proxmox web interface

Introduction

I often find myself ssh'ing into my servers and checking my systemd service logs with $ journalctl -f -u {name}.service. One day I got tired of this and wanted all of my important logs in once place (Amazon AWS Cloudwatch). To my dismay, there weren't any real good tutorials on how to do so. So, voilà.

Steps

Overall, it's a fairly simple process consisting of the following few steps.

1. Modify the service file

Open the service file with $ sudo vi /lib/systemd/system/{name}.service

Modify the [Service] section:

Install Proxmox and a RancherOS VM with Portainer to manage docker containers

WARNING MAY BE INCORRECT AND INCOMPLETE, USE AT YOUR OWN RISK

I have tried this setup and although it works and may be good for ceratin circumstances I would advise using ubuntu as the base with docker, docker-compose, and portainer. https://gist.github.com/mow4cash/626275e095f7f90898944a85d66b3be6

Link to my docker run file https://gist.github.com/mow4cash/6a25343cdeb0cd115f263dea0a3b623d

Install Rancher Manager With Lets Encrypt (Linux)

Infrastructure

Domain Name
Ability to make DNS Changes
Debian 11 Virtual Machine (Should work with Ubuntu)
Port 80 & 443 must be accessible for Let's Encrypt to verify and issue certificates

Pick a subdomain and create a DNS entry pointing to the IP Address that will be assigned to the Rancher Server

Docker compose as a systemd unit

Create file /etc/systemd/system/[email protected]. SystemD calling binaries using an absolute path. In my case is prefixed by /usr/local/bin, you should use paths specific for your environment.

[Unit]
Description=%i service with docker compose
PartOf=docker.service
After=docker.service

The repository for the assignment is public and Github does not allow the creation of private forks for public repositories.

The correct way of creating a private frok by duplicating the repo is documented here.

For this assignment the commands are:

Create a bare clone of the repository. (This is temporary and will be removed so just do it wherever.)

git clone --bare [email protected]:usi-systems/easytrace.git

	<?php

	$hostname = 'host.example.com';
	$port = 22;
	$username = 'your_username';
	$ssh_key = './ssh/id_rsa';
	$ssh_pubkey = './ssh/id_rsa.pub';
	$src_file = 'testupload.txt';
	$dest_file = "remoteDirectory/{$src_file}";

	// Just before switching jobs:
	// Add one of these.
	// Preferably into the same commit where you do a large merge.
	//
	// This started as a tweet with a joke of "C++ pro-tip: #define private public",
	// and then it quickly escalated into more and more evil suggestions.
	// I've tried to capture interesting suggestions here.
	//
	// Contributors: @r2d2rigo, @joeldevahl, @msinilo, @_Humus_,
	// @YuriyODonnell, @rygorous, @cmuratori, @mike_acton, @grumpygiant,

	configure

	# Configure Firewall
	set firewall ipv6-name IPV6WAN_IN description 'IPV6WAN to internal'
	set firewall ipv6-name IPV6WAN_IN default-action drop

	set firewall ipv6-name IPV6WAN_IN rule 10 action accept
	set firewall ipv6-name IPV6WAN_IN rule 10 state established enable
	set firewall ipv6-name IPV6WAN_IN rule 10 state related enable
	set firewall ipv6-name IPV6WAN_IN rule 10 log disable

	# TODO: replace :token, :user, and :repo
	curl -H "Authorization: token :token" \
	-H 'Accept: application/vnd.github.everest-preview+json' \
	"https://api.github.com/repos/:user/:repo/dispatches" \
	-d '{"event_type": "awesomeness", "client_payload": {"foo": "bar"}}'