fbrendel

Proxmox:

balloon: 0
bootdisk: scsi0
cores: 2
cpu: host
ide2: none,media=cdrom
memory: 3072
name: elvmlx39
net0: virtio=1A:78:93:9D:DC:48,bridge=vmbr0

fbrendel

# ethtool --show-offload eno1
Features for eno1:
rx-checksumming: on
tx-checksumming: on
        tx-checksum-ipv4: on
        tx-checksum-ip-generic: off [fixed]
        tx-checksum-ipv6: on
        tx-checksum-fcoe-crc: off [fixed]
        tx-checksum-sctp: off [fixed]
scatter-gather: on

lukasnellen

Docker(-compose) with shorewall

The shorewall documentation explains in http://shorewall.org/Docker.html how to configure shorewall for use with docker. The problem with the configuration is that it only allows connections from the host to the main bridge docker0. Connections to other networks on dynamically created bridges, with names starting by default with br-, is blocked. Instead of the recommended contents of /etc/shorewall/interfaces, use wild-card interface names as follows:

#ZONE	INTERFACE	OPTIONS
#dock	docker0		bridge     # disabled default recommendation
dock 	docker0		physical=docker+,routeback=1
dock 	br		physical=br-+,routeback=1

EugenMayer

# we no longer use /tmp sinc it is a tmpfs / in memory

mkdir ~/tmp
cd ~/tmp

sysbench --file-fsync-freq=1 --num-threads=16 --test=fileio --file-total-size=1G --file-test-mode=rndrw --file-rw-ratio=2 cleanup > /dev/null
sysbench --file-fsync-freq=1 --num-threads=16 --test=fileio --file-total-size=1G --file-test-mode=rndrw --file-rw-ratio=2 prepare > /dev/null
sysbench --file-fsync-freq=1 --num-threads=16 --test=fileio --file-total-size=1G --file-test-mode=rndrw --file-rw-ratio=2 run

# when you are done testing

offlinehoster

# Maintainer: Ashley Whetter <(firstname) @ awhetter.co.uk>
# Co-Maintainer: NicoHood <archlinux {cat} nicohood {dog} de>
# PGP ID: 97312D5EB9D7AE7D0BD4307351DAE9B7C1AE9161
# Contributor: Eothred <yngve.levinsen@gmail.com>

pkgname=spotify
pkgver=1.1.42.622
epoch=1
_commit=gbd112320
_ver_x86_64=37

karlvr

Migrate Maven packages from Sonatype Nexus to GitHub Packages

This gist describes the process we've used to migrate our Maven package repository from Sonatype Nexus to GitHub Packages. The same process could be used for migrating any Maven package repo that is in the standard layout.

We created a special repository on GitHub to hold all of our Maven packages. You might decide to migrate packages to different repositories, in which case invoke the script multiple times.

The script uses find to look for all of the folders containing poms and upload them. You specify the folder