Hu Wan huwan

Setting up email with SMTP on Ubuntu/Debian Servers

I used to sift trough my shell history and bookmarks every time I set up a new testing server in order to be able to send mails. So this should help...

Be aware don't use ssmtp anymore. It's unmaintained and has been removed from Debian and Ubuntu will most definitely follow suit.

Install msmtp

With GitHub Actions, a workflow can publish artifacts, typically logs or binaries. As of early 2020, the life time of an artifact is hard-coded to 90 days (this may change in the future). After 90 days, an artifact is automatically deleted. But, in the meantime, artifacts for a repository may accumulate and generate mega-bytes or even giga-bytes of data files.

It is unclear if there is a size limit for the total accumulated size of artifacts for a public repository. But GitHub cannot reasonably let multi-giga-bytes of artifacts data accumulate without doing anything. So, if your workflows regularly produce large artifacts (such as "nightly build" procedures for instance), it is wise to cleanup and delete older artifacts without waiting for the 90 days limit.

Using the Web page for the "Actions" of a repository, it is possible to browse old workflow runs and manually delete artifacts. But the procedure is slow and tedious. It is fine to delete one selected artifact. It is not for a regular cleanup. We need

With GitHub Actions, a workflow can publish artifacts, typically logs or binaries. As of early 2020, the life time of an artifact is hard-coded to 90 days (this may change in the future). After 90 days, an artifact is automatically deleted. But, in the meantime, artifacts for a repository may accumulate and generate mega-bytes or even giga-bytes of data files.

It is unclear if there is a size limit for the total accumulated size of artifacts for a public repository. But GitHub cannot reasonably let multi-giga-bytes of artifacts data accumulate without doing anything. So, if your workflows regularly produce large artifacts (such as "nightly build" procedures for instance), it is wise to cleanup and delete older artifacts without waiting for the 90 days limit.

Using the Web page for the "Actions" of a repository, it is possible to browse old workflow runs and manually delete artifacts. But the procedure is slow and tedious. It is fine to delete one selected artifact. It is not for a regular cleanup. We need

	################################################################################
	# Method 1: Install using rpm packages (credit to DarkMukke)
	#

	rpm -Uvh http://mirror.ghettoforge.org/distributions/gf/gf-release-latest.gf.el7.noarch.rpm
	rpm --import http://mirror.ghettoforge.org/distributions/gf/RPM-GPG-KEY-gf.el7

	# WARNING: removing vim-minimal uninstalls `sudo` if you skip the second step
	# make sure to at least run `yum install sudo`
	yum -y remove vim-minimal vim-common vim-enhanced

	https://gist.github.com/application2000/73fd6f4bf1be6600a2cf9f56315a2d91

	sudo apt-get update -y && \
	sudo apt-get upgrade -y && \
	sudo apt-get dist-upgrade -y && \
	sudo apt-get install build-essential software-properties-common -y && \
	sudo add-apt-repository ppa:ubuntu-toolchain-r/test -y && \
	sudo apt-get update -y && \
	sudo apt-get install gcc-7 g++-7 -y && \
	sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-7 60 --slave /usr/bin/g++ g++ /usr/bin/g++-7 && \

	### NOT A SCRIPT, JUST A REFERENCE!

	# install dante-server
	sudo apt update
	sudo apt install dante-server

	# or download latest dante-server deb for Ubuntu, works for 16.04 / 18.04 / 20.04:
	wget http://archive.ubuntu.com/ubuntu/pool/universe/d/dante/dante-server_1.4.2+dfsg-7build5_amd64.deb
	# or older version:
	wget http://ppa.launchpad.net/dajhorn/dante/ubuntu/pool/main/d/dante/dante-server_1.4.1-1_amd64.deb

	#/bin/bash

	launchctl stop com.qiuyuzhou.shadowsocksX-NG.local
	launchctl stop com.qiuyuzhou.shadowsocksX-NG.http
	launchctl stop com.qiuyuzhou.shadowsocksX-NG.kcptun

	sudo rm -rf /Applications/ShadowsocksX-NG*.app
	sudo rm -rf /Library/Application\ Support/ShadowsocksX-NG
	sudo rm -rf ~/Library/Application\ Support/ShadowsocksX-NG
	sudo rm -rf ~/Library/LaunchAgents/com.qiuyuzhou.shadowsocksX-NG.*

	while !isOnOpenSwitch {
	while !isBlocked {
	if isOnGem {
	collectGem()
	}
	if isOnClosedSwitch {
	toggleSwitch()
	}
	moveForward()
	}

	#!/usr/bin/env bash

	#
	# Setup automatic sync from a Github upstream repository to a fork
	# - a branch "actions" will be created (or re-used) to hold the Github action to run
	# - sync is done each hour
	# - branch 'actions' needs to be the default branch of your fork (=> settings)
	# - the script is able to both create and update and rewrite the sync script if you modify this script file
	#
	# Author: Mathiue Carbou