Diego changeme

docker-compose.yml

version: '3.6'

services:
  minio:
    image: minio/minio:RELEASE.2020-01-03T19-12-21Z
    container_name: minio
    volumes:

WordPress: Performance & Development tips

Let's Encrypt / Dovecot / Postfix / UFW firewall / Certbot

This tutorial describes how to install TLS to a mail server consisting of Postfix and/or Dovecot by using Let's Encrypt certificates with automatic renewing and firewall management.

The system used for this tutorial was:

$ lsb_release -idrc
Distributor ID: Ubuntu

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

Safest way to clean up boot partition - Ubuntu 14.04LTS-x64, Ubuntu 16.04LTS-x64

Reference

Case I: if /boot is not 100% full and apt is working

1. Check the current kernel version

$ uname -r

OpenVPN Server and certificate management on MikroTik

Langkah migrasi mail server postfix ke zimbra

Migrasi account

Copy script berikut dan beri nama backup.php. Simpan ke server lama.

#!/usr/bin/php

// Postfixadmin (http://postfixadmin.sourceforge.net/) to Zimbra

Install XenServer 6.5 on softraid

Warning! From default installation of XenServer 6.5 modules of raid, nfs and etc in kernel disabled. "Thanks for developers." In this variation: XenServer 6.5 withoud patches and service packs, kernel 3.10.0+2, 2 disks WD 2 TB

Turn on raid support##

Make module file (change raidX for you raid level):

 # echo "modprobe raid1" > /etc/sysconfig/modules/raid.modules

	#!/bin/bash
	# file: ttfb.sh
	# curl command to check the time to first byte
	# usage
	# 1. ./ttfb.sh "https://google.com"
	# 2. seq 10 \| xargs -Iz ./ttfb.sh "https://google.com"

	curl -o /dev/null \
	-H 'Cache-Control: no-cache' \
	-s \

	# Sample Nginx config with sane caching settings for modern web development
	#
	# Motivation:
	# Modern web development often happens with developer tools open, e. g. the Chrome Dev Tools.
	# These tools automatically deactivate all sorts of caching for you, so you always have a fresh
	# and juicy version of your assets available.
	# At some point, however, you want to show your work to testers, your boss or your client.
	# After you implemented and deployed their feedback, they reload the testing page – and report
	# the exact same issues as before! What happened? Of course, they did not have developer tools
	# open, and of course, they did not empty their caches before navigating to your site.