WeboAp weboAp

VS Code Configuration

Export VSCode Extensions:

code --list-extensions | xargs -L 1 echo code --install-extension # Unix

code --list-extensions | % { "code --install-extension $_" } # Windows PowerShell

Shortcuts:

Mistakes to Avoid: Docker Antipatterns

Whichever route you take to implementing containers, you’ll want to steer clear of common pitfalls that can undermine the efficiency of your Docker stack.

Don’t run too many processes inside a single container

The beauty of containers—and an advantage of containers over virtual machines—is that it is easy to make multiple containers interact with one another in order to compose a complete application. There is no need to run a full application inside a single container. Instead, break your application down as much as possible into discrete services, and distribute services across multiple containers. This maximizes flexibility and reliability.

Don’t install operating systems inside Docker containers

It is possible to install a complete Linux operating system inside a container. In most cases, however, this is not necessary. If your goal is to host just a single application or part of an application in the container, you need to install only the essential

Bucket Policy

Bucket policy is an access policy available for you to grant anonymous permissions to your Minio resources. Bucket policy uses JSON-based access policy language.

This section presents a few examples of typical use cases for bucket policies. The policies use testbucket strings in the resource value. To test these policies, you need to replace these strings with your bucket name. For more information please read Amazon S3 access policy language

Granting Read-Only Permission to an Anonymous User

The following example policy grants the s3:GetObject permission to any public anonymous users. This permission allows anyone to read the object data under testbucket, which is useful for when you have publicly readable assets. A typical example is a website assets stored in testbucket.

HOWTO: Create Your Own Self-Signed Certificate with Subject Alternative Names Using OpenSSL in Ubuntu Bash for Window

Overview

My main development workstation is a Windows 10 machine, so we'll approach this from that viewpoint.

Recently, Google Chrome started giving me a warning when I open a site that uses https and self-signed certificate on my local development machine due to some SSL certificate issues like the one below:

	apiVersion: v1
	kind: Namespace
	metadata:
	name: rook-ceph-system
	---
	apiVersion: apiextensions.k8s.io/v1beta1
	kind: CustomResourceDefinition
	metadata:
	name: cephclusters.ceph.rook.io
	spec:

	version: '3'
	services:
	fpm:
	image: sbvr/laravel-fpm:2.1.2
	volumes:
	- app:/var/www
	networks:
	- appnet

	worker:

-- hosts: all
-  tasks:
-  - name: Ansible delete file wildcard
-    find:
-      paths: /etc/wild_card/example
-      patterns: "^he.*.txt"
-      use_regex: true
-    register: wildcard_files_to_delete
-  - name: Ansible remove file wildcard

	# start with this
	wget http://eu.ceph.com/rpm-luminous/el7/noarch/ceph-release-1-1.el7.noarch.rpm
	sudo rpm -Uvh ceph-release-1-1.el7.noarch.rpm

	# this is required for the ADMIN node only
	sudo yum install python-jinja2
	wget http://mirror.centos.org/centos/7/extras/x86_64/Packages/python-itsdangerous-0.23-2.el7.noarch.rpm
	wget http://mirror.centos.org/centos/7/extras/x86_64/Packages/python-werkzeug-0.9.1-2.el7.noarch.rpm
	wget http://mirror.centos.org/centos/7/extras/x86_64/Packages/python-flask-0.10.1-4.el7.noarch.rpm
	sudo rpm -i python-itsdangerous-0.23-2.el7.noarch.rpm python-flask-0.10.1-4.el7.noarch.rpm python-werkzeug-0.9.1-2.el7.noarch.rpm

	# first get the PPA repository driver
	sudo add-apt-repository ppa:graphics-drivers/ppa

	# install nvidai driver
	sudo apt install nvidia-384 nvidia-384-dev

	# install other import packages
	sudo apt-get install g++ freeglut3-dev build-essential libx11-dev libxmu-dev libxi-dev libglu1-mesa libglu1-mesa-dev

	# CUDA 9 requires gcc 6

	# Assumming we have 3 nodes
	NODE1=10.0.1.1
	NODE2=10.0.1.2
	NODE3=10.0.1.3

	# Configure the server
	ssh root@NODE1 apt-get install -y glusterfs-server
	ssh root@NODE2 apt-get install -y glusterfs-server
	ssh root@NODE3 apt-get install -y glusterfs-server
	ssh root@NODE1 gluster peer probe NODE2