nguyen127001

Override the entrypoint in docker-compose.yml for the MariaDB Docker container by adding:

entrypoint: mysqld_safe --skip-grant-tables --user=mysql

The start up the Docker Compose stack:

$> docker-compose up -d

Then login to the Docker container:

Introduction

I often find myself ssh'ing into my servers and checking my systemd service logs with $ journalctl -f -u {name}.service. One day I got tired of this and wanted all of my important logs in once place (Amazon AWS Cloudwatch). To my dismay, there weren't any real good tutorials on how to do so. So, voilà.

Steps

Overall, it's a fairly simple process consisting of the following few steps.

1. Modify the service file

Open the service file with $ sudo vi /lib/systemd/system/{name}.service

Modify the [Service] section:

Nginx TLS SNI routing, based on subdomain pattern

Nginx can be configured to route to a backend, based on the server's domain name, which is included in the SSL/TLS handshake (Server Name Indication, SNI).
This works for http upstream servers, but also for other protocols, that can be secured with TLS.

prerequisites

at least nginx 1.15.9 to use variables in ssl_certificate and ssl_certificate_key.
check nginx -V for the following:
```
...
TLS SNI support enabled
```

Example

This is simple example showing:

Service service-alpha in service-alpha namespace
Service service-beta in service-beta namespace
Nginx Ingress controller in kube-ingress namespace
Ingress called ingress-demo inside service-alpha namespace
Ingress called ingress-demo inside service-beta namespace

Steps:

Install ingress on AKS. my demo cluster does not have rbac enabled that's why there is => --set rbac.create=false

inode

là CẤU TRÚC DỮ LIỆU trong UNIX filesystem, dùng để chứa các thông tin về file (owner, permission, time, disk block location - địa chỉ trên ổ cứng thực sự chứa dữ liệu file) - CHÚ Ý: inode không chứa tên file
ít gặp khi vận hành hệ thống (chỉ xuất hiện khi ổ cứng hết inode không tạo được thêm file, xem bằng df -i)
thường xuyên được hỏi khi phỏng vấn các công ty nước ngoài
là khái niệm ở level tương đối thấp (UNIX filesystem: ext2, ext3, ext4, ...)
đã ở đó từ những năm 197x
wikipedia có thông tin khá đầy đủ https://en.wikipedia.org/wiki/Inode

hardlink

Let's say we can a blog hosted as Wordpress.com but visible on our custom domain in subpath due to SEO. WordPress.com supports changing domain/subdomain but not path.

We could either make our own installation, change hosting provier or make nginx proxy with URL rewrites.

WP blog: https://example.wordpress.com/
Desired site: http://example.com/blog/

This tutorial is inpsired by http://marsbard.github.io/2016-07-30-replace-urls-behind-nginx-reverse-proxy/.


	proxy_cache_path /tmp/cacheapi levels=1:2 keys_zone=microcacheapi:100m max_size=1g inactive=1d use_temp_path=off;
	server {
	listen 443 ssl http2 default_server;
	listen [::]:443 ssl http2 default_server;
	server_name example.com;

	location /api/ {
	# Rate Limiting
	limit_req zone=reqlimit burst=20; # Max burst of request

	version: "3"
	services:

	postgres-db:
	image: postgres
	restart: always
	ports:
	- 5432:5432
	environment:
	POSTGRES_PASSWORD: postgres


	proxy_cache_path /tmp/cacheapi levels=1:2 keys_zone=microcacheapi:100m max_size=1g inactive=1d use_temp_path=off;
	server {
	listen 443 ssl http2 default_server;
	listen [::]:443 ssl http2 default_server;
	server_name example.com;

	location /api/ {
	# Rate Limiting
	limit_req zone=reqlimit burst=20; # Max burst of request

	sudo amazon-linux-extras install epel -y
	sudo yum install stress -y