maazghani

[ dev@dev:storefront (develop) ] 
 > sudo npm update -g
[sudo] password for dev: 
npm http GET https://registry.npmjs.org/gulp
npm http GET https://registry.npmjs.org/bower
npm http GET https://registry.npmjs.org/sails
npm http 304 https://registry.npmjs.org/gulp
npm http 304 https://registry.npmjs.org/bower
npm http 304 https://registry.npmjs.org/sails
npm http GET https://registry.npmjs.org/archy

maazghani

server {
    listen 8080;

    root /home/ottemo/dashboard/dist/;
    index index.html;
    
    location / {
        try_files $uri $uri/ =404;
    }
}

maazghani

apiVersion: v1beta1
kind: Pod
id: ottemo
desiredState:
  manifest:
    version: v1beta1
    id: ottemo
    containers:
      - name: foundation 
        image: foundation

maazghani

; Domain: karigran.com
; Exported (y-m-d hh:mm:ss): 2015-05-30 15:15:58
;
; This file is intended for use for informational and archival
; purposes ONLY and MUST be edited before use on a production
; DNS server.
;
; In particular, you must update the SOA record with the correct
; authoritative name server and contact e-mail address information,
; and add the correct NS records for the name servers which will

maazghani

stakeholders:

• @maazghani

parts requests

• 3 raspberry pi 3b+/4/zero
• k3s - lightweight k8s for IoT/ARM
• tailscale - software defined mesh VPN with private DNS built in

maazghani

[AWS Service annotations](https://github.com/kubernetes/kubernetes/blob/v1.12.0/pkg/cloudprovider/providers/aws/aws.go)
---

- `service.beta.kubernetes.io/aws-load-balancer-access-log-emit-interval` (in minutes)
- `service.beta.kubernetes.io/aws-load-balancer-access-log-enabled` (true|false)
- `service.beta.kubernetes.io/aws-load-balancer-access-log-s3-bucket-name`
- `service.beta.kubernetes.io/aws-load-balancer-access-log-s3-bucket-prefix`
- `service.beta.kubernetes.io/aws-load-balancer-additional-resource-tags` (comma-separated list of key=value)
- `service.beta.kubernetes.io/aws-load-balancer-backend-protocol` (http|https|ssl|tcp)
- `service.beta.kubernetes.io/aws-load-balancer-connection-draining-enabled` (true|false)

maazghani

parts requests

• 3 raspberry pi zeros
• k3s - lightweight k8s for IoT/ARM
• wireguard tailscale mesh vpn

maazghani

Terminal Commands

git

git clone [the-url]
ex: git clone github.com/maazghani/site.git

# pull the latest code
git pull

maazghani

Terminal Commands

git

git clone [the-url]
ex: git clone github.com/maazghani/site.git

# pull the latest code
git pull

maazghani

Clickhouse Architecture

• ClickHouse is a columnar database that supports SQL queries. It stores data in columns rather than rows, which makes it very efficient for analytical queries on large datasets.
• It is designed to handle massive amounts of data and can scale horizontally across multiple servers.
• ClickHouse has a pluggable storage engine architecture, which allows it to work with different types of storage like local disks, distributed file systems, object stores, and cloud storage.
• ClickHouse also supports replication and sharding for high availability and performance.

Use Cases

• ClickHouse is designed for OLAP (online analytical processing) workloads, which involve running complex analytical queries on large datasets.
• It is commonly used for time-series data, log analytics, clickstream analysis, and business intelligence.
• ClickHouse is often used in conjunction with other databases like MySQL or PostgreSQL, which are used for OLTP (online transaction processing) workloads.