Phạm Tiến Thành tienthanh2509

Transparent proxy for Docker containers

If the Docker host is placed inside a proxy server, it needs to add the proxy configuration to each Dockerfile such as ENV http_proxy.

Following allows transparent access from the container to outside without any proxy configuration.

Set up the transparent proxy
Apply iptables rule for the transparent proxy

Install Terminator (shell)

sudo add-apt-repository ppa:gnome-terminator
sudo apt-get update
sudo apt-get install terminator

Terminator should be setup as default now. Restart your terminal (shortcut: "Ctrl+Alt+T").

Install ZSH

Zimbra Letsencrypt SSL Renew

Zimbra Version: Release 8.6.0_GA_1153.RHEL7_64_20141215151110 RHEL7_64 FOSS edition

Based on Zimbra Article KB 22434 : https://wiki.zimbra.com/wiki/Installing_a_LetsEncrypt_SSL_Certificate

Let's Begin

Log on Zimbra user then stop proxy and mail box service for renew proccess.

su zimbra

Steps to build Android kernel and system for LXC:

Download Android SDK, NDK, system and kernel source code;
Download modified lxc and libcap source code (ppoffiec/lxc-android, ppoffice/libcap-android)
Build Android system from source first so that we can link to its shared library when we build lxc (or maybe we don't have to);
Modify Android kernel config and make sure lxc-checkconfig does not report any missing features. Then build kernel;
Modify Android system/core/rootdir/init.rc according to init.rc.diff. Make sure you mount all the cgroup subsystems needed (cpu, cpuacct, cpuset, memory, pids, devices, freezer, blkio) under /sys/fs/cgruop, otherwise lxc won't find them;
Rebuilt the Android system image so that the modified init.rc is in the image;
Fire up the emulator with custom kernel (emulator -kernel kernel-file-path) and use adb shell and dmesg to check if everything is doing ok.

Prevent creation of vmmem files in VMware (Windows)

Issue

VMWare creates .vmem files to back the guest RAM. On the host this causes disk thrashing especially during powering on and off the guest.

Solution

Add the following lines to the .vmx file to prevent creation of .vmem files. This will reduce disk IO and VM performance will improve especially on non-SSD disks.

Proxmox VE 6.x release includes a feature to add custom cloud-init configs. Unfortunately there is poor documentation, so I had to figure this out by adding pieces of information together.

The custom cloud-init files (user-data, meta-data, network-config)

The cloud-init files need to be stored in a snippet. This is not very well documented:

Go to Storage View -> Storage -> Add -> Directory
Give it an ID such as snippets, and specify any path on your host such as /snippets
Under Content choose Snippets and de-select Disk image (optional)
Upload (scp/rsync/whatever) your user-data, meta-data, network-config files to your proxmox server in /snippets/snippets/ (the directory should be there if you followed steps 1-3)

How to download old versions of Chrome

Click here to download old versions of Chrome for Linux, Mac and Windows.

The download_url field of the desired section houses the URL to the download.

Alternatively, for not too old versions, you can get it directly here.

	<?php
	/**
	* A helper file for Laravel 5, to provide autocomplete information to your IDE
	* Generated for Laravel 5.5.13 on 2017-09-28.
	*
	* @author Barry vd. Heuvel <[email protected]>
	* @see https://github.com/barryvdh/laravel-ide-helper
	*/
	namespace {
	exit("This file should not be included, only analyzed by your IDE");

	# import config.
	# You can change the default config with `make cnf="config_special.env" build`
	cnf ?= config.env
	include $(cnf)
	export $(shell sed 's/=.*//' $(cnf))

	# import deploy config
	# You can change the default deploy config with `make cnf="deploy_special.env" release`
	dpl ?= deploy.env
	include $(dpl)

	svc usb setFunction rndis
	ip addr add 192.168.137.2/24 dev rndis0
	ip link set dev rndis0 up
	ip route add default via 192.168.137.1 dev rndis0
	ndc resolver setnetdns rndis0 local 8.8.8.8 8.8.4.4