Vladimir K kramarama

Headless Ethminer (nVidia) Setup Guide

Cian Johnston, July 2017

WARNING: THESE WORDS ARE OLD AND MAY NOT WORK FOR YOU IN THESE NEW AND INTERESTING TIMES.

A couple of weeks ago, I decided I should put my gaming rig to work crypto mining. I did not expect to make any significant profit on this, it was more of a fun project to set up. However, there were a large number of tutorials and guides already out there, and many were more than a year out of date.

This guide assumes the reader already has a crypto wallet set up, is comfortable with Linux and the command line, and knows how to use Google if they run into problems.

The end result is an Ubuntu 16.04 LTS headless server running CUDA ethminer via systemd.

Download docker-compose.yml to dir named sentry
Change SENTRY_SECRET_KEY to random 32 char string
Run docker-compose up -d
Run docker-compose exec sentry sentry upgrade to setup database and create admin user
(Optional) Run docker-compose exec sentry pip install sentry-slack if you want slack plugin, it can be done later
Run docker-compose restart sentry
Sentry is now running on public port 9000

https://docs.docker.com/compose/compose-file/#env_file

I have been an aggressive Kubernetes evangelist over the last few years. It has been the hammer with which I have approached almost all my deployments, and the one tool I have mentioned (shoved down clients throats) in almost all my foremost communications with clients, and it was my go to choice when I was mocking my first startup (saharacluster.com).

A few weeks ago Docker 1.13 was released and I was tasked with replicating a client's Kubernetes deployment on Swarm, more specifically testing running compose on Swarm.

And it was a dream!

All our apps were already dockerised and all I had to do was make a few modificatons to an existing compose file that I had used for testing before prior said deployment on Kubernetes.

And, with the ease with which I was able to expose our endpoints, manage volumes, handle networking, deploy and tear down the setup. I in all honesty see no reason to not use Swarm. No mission-critical feature, or incredibly convenient really nice to have feature in Kubernetes that I'm go

Debian ixgbe module compilation

Some OVH dedicated server does not supports installing Debian original kernel due to hardware support issue.

Most common issue is the network adapter card.

Resources

Intel ixgbe linux drivers : https://downloadcenter.intel.com/download/14687
OVH forum : https://forum.ovh.co.uk/showthread.php?5616-Standard-Kernels-with-Ubuntu-Debian&p=73788&viewfull=1#post73788

	class Makepasswd < Formula
	desc "Makepasswd random password generator"
	homepage "https://packages.debian.org/sid/makepasswd"
	url "http://ftp.debian.org/debian/pool/main/m/makepasswd/makepasswd_1.10.orig.tar.gz"
	sha256 "41491f361d810f9bb3e08b40df3c3034faec306d434dab15534e19023f91a75c"

	def install
	bin.install "makepasswd"
	man1.install "makepasswd.1"
	end

	#! /bin/bash

	set -e -o pipefail

	function usage {
	cat - <<USAGE
	Usage:
	$0 -n namespace -s source -d destination
	USAGE
	}

	#!/usr/bin/env bash

	# A helper for kind to create and delete clusters with untrusted local registry.
	# Based on https://kind.sigs.k8s.io/docs/user/local-registry/
	#
	# Note: kind 0.10.0

	# Settings for kind cluster
	CLUSTER_NAME="kube-19"
	KIND_NODE_IMAGE="kindest/node:v1.19.7"

	function listFolders(folder) {
	var sheet = SpreadsheetApp.getActiveSheet();
	sheet.appendRow(["Name", "Sharing Access", "Sharing Permission", "Get Editors", "Get Viewers", "Date", "Size", "URL", "Download", "Description", "Type"]); //writes the headers

	//var folder = DriveApp.getFolderById("INSERT_YOUR_FILE_ID");//that long chunk of random numbers/letters in the URL when you navigate to the folder
	//getLooseFiles(folder, sheet);
	//getSubFolders(folder, sheet);

	//instead of getting folder by ID rather get all folders and cycle through each. Note this will miss loose files in parent directory.
	var folder = DriveApp.getFolders()

	---
	apiVersion: extensions/v1beta1
	kind: DaemonSet
	metadata:
	name: oom-killer
	namespace: kube-system
	labels:
	k8s-app: oom-killer
	spec:
	selector:

	#!/bin/bash

	BASE_PATH=/var/opt/gitlab/gitlab-rails/shared/registry/docker/registry/v2/repositories

	DRY_RUN=0
	KEEP_LAST_IMAGES=10
	RUN_GARBAGE_COLLECTOR=0
	GITLAB_CTL_COMMAND=`which gitlab-ctl`