neumachen

#!/bin/zsh

### Added by Zinit's installer
if [[ ! -f $HOME/.zinit/bin/zinit.zsh ]]; then
    print -P "%F{33}▓▒░ %F{220}Installing %F{33}DHARMA%F{220} Initiative Plugin Manager (%F{33}zdharma/zinit%F{220})…%f"
    command mkdir -p "$HOME/.zinit" && command chmod g-rwX "$HOME/.zinit"
    command git clone https://github.com/zdharma/zinit "$HOME/.zinit/bin" && \
        print -P "%F{33}▓▒░ %F{34}Installation successful.%f%b" || \
        print -P "%F{160}▓▒░ The clone has failed.%f%b"
fi

neumachen

This (and related gists) captures how i created my docker swarm architecture. This is intended mostly for my own notes incase i need to re-creeate anything later! As such expect some typos and possibly even an error...

Installation Step-by-Step

Each major task has its own gist, this is to help with maitainability long term.

1. Install Debian VM for each docker host
2. install Docker
3. Configure Docker Swarm
4. Install Portainer
5. Install KeepaliveD
6. glusterFS disk prep, install & config

neumachen

blueprint:
  name: Turn Off Switches At Sunrise
  description: Turn off the following switches at sunrise
  domain: automation
  input:
    # Create a variable for identifying the light to act upon
    target_switch:
      name: Switches
      description: This is the switch (or switches) that will be deactivated at sunrise
      # Use a selector, to pick the light(s)

neumachen

blueprint:
  name: Turn On Switches At Sunset
  description: Turn on the following switches at sunset
  domain: automation
  input:
    # Create a variable for identifying the light to act upon
    target_switch:
      name: Switches
      description: This is the switch (or switches) that will be activated at sunset
      # Use a selector, to pick the light(s)

neumachen

if [ ! -f .env ]
then
  export $(cat .env | xargs)
fi

neumachen

// A generic doubly-linked list

package list

// the zero value is ready to use.
type List[T any] struct {
	root Element[T]
	Len  int
}

neumachen

The following snippet contains an example for GoLang Generics for Structs:

package main

import "fmt"

// Structs definition
type ObjectOne struct {
	Name string      `json:"name"`

neumachen

if you can access to the GUI environment, It is very easy using "disks" application.

or might be easy with gdisk/fdisk ?   I'm not sure about this.  

------------------------------------------------------------------------  

see the reference for more detail, if you want.
https://richardstechnotes.wordpress.com/2015/12/18/setting-up-an-nvme-ssd-on-ubuntu-14-04-lts/   http://takatakamanbou.hatenablog.com/entry/2015/10/25/235600 : Japanese website

neumachen

#!/bin/bash
# (c) 2020 [email protected]
# SPDX-License-Identifier: Apache-2.0 OR MIT
#
# This script installs support for building multi-architecture docker images
# with docker buildx on CI/CD pipelines like Github Actions or Travis. It is
# assumed that you start of with a fresh VM every time you run this and have to
# install everything necessary to support 'docker buildx build' from scratch.
#
# Example usage in Travis stage:

neumachen

       --label "traefik.enable=true" \
        --label "traefik.protocol=http" \
 	     --label "traefik.first.port=80" \
  		 --label "traefik.first.frontend.rule=Host:web1.example.com" \
 	     --label "traefik.second.port=8080" \
  		 --label "traefik.second.frontend.rule=Host:web2.example.com" \
  	
    
 Above labels will allow us to forward web1.example.com to docker container port 80 and web2.example.com to same container's port 8080