liviaerxin

FastAPI and Uvicorn Logging

When running FastAPI app, all the logs in console are from Uvicorn and they do not have timestamp and other useful information. As Uvicorn applies python logging module, we can override Uvicorn logging formatter by applying a new logging configuration.

Meanwhile, it's able to unify the your endpoints logging with the Uvicorn logging by configuring all of them in the config file log_conf.yaml.

Before overriding:

uvicorn main:app --reload

genesysflow

apiVersion: traefik.containo.us/v1alpha1
kind: ServersTransport
metadata:
  name: insecure-transport
  namespace: default
spec:
  insecureSkipVerify: true
---
apiVersion: networking.k8s.io/v1
kind: Ingress

GuillaumeFalourd

{
  "token": "***",
  "job": "github-context",
  "ref": "refs/pull/16/merge",
  "sha": "b4f1729888b5c99abdf8a7a250ecc6cff1e180be",
  "repository": "GuillaumeFalourd/poc-github-actions",
  "repository_owner": "GuillaumeFalourd",
  "repositoryUrl": "git://github.com/GuillaumeFalourd/poc-github-actions.git",
  "run_id": "974568708",
  "run_number": "2",

nebhead

The following is capturing instructions on how to add custom naming for an Arduino Leonardo (or generic pro-micro) for my Arcade Controller device. I wanted to have a simple record so that when I inevitably come back to this someday I can recall how I accomplished this. Reference was taken from the following YouTube video (https://youtu.be/hoCOq9Ngp44?t=1156) at approximately 19m16s.

WINDOWS Instructions:

Create a new set of folders: ~\Documents\Arduino\hardware\daemonbite\avr

Copy everything from C:\Program Files (x86)\Arduino\hardware\arduino\avr to this new folder.

G4brym

version: "3.4"
x-environment: &default-environment
    DATABASE_URL: postgres://postgres:postgres@postgres:5432/postgres
    SECRET_KEY: your-secret-here
    PORT: 8000
    GLITCHTIP_DOMAIN: https://glitchtip.yourcompany.com
    EMAIL_URL: smtp+tls://smtp-user:smtp-password@email-smtp.eu-west-1.amazonaws.com:587
    DEFAULT_FROM_EMAIL: glitchtip@yourcompany.com
    ENABLE_OPEN_USER_REGISTRATION: "True"
x-depends_on: &default-depends_on

icebob

# Install K3S
curl -sfL https://get.k3s.io | sh -

# Copy k3s config
mkdir $HOME/.kube
sudo cp /etc/rancher/k3s/k3s.yaml $HOME/.kube/config
sudo chmod 644 $HOME/.kube/config

# Check K3S 
kubectl get pods -n kube-system

magickatt

export GITHUB_USER=magickatt
export GITHUB_TOKEN=secret
export GITHUB_REPOSITORY=magickatt/ContainerisingLegacyApplicationsTalk
git clone https://${GITHUB_USER}:${GITHUB_TOKEN}@github.com/${GITHUB_REPOSITORY}

sergeyklay

Journalctl Cheat Sheet

Configuration

Permissions

To see messages from other users and the system as well as performing various log operations from a regular user add it to the group:

sudo usermod -aG systemd-journal $USER

roommen

#!/bin/bash
sudo yum install gcc -y
sudo yum install openssl-devel -y
sudo yum install zlib-devel -y
sudo yum install mlocate -y
sudo yum install autoconf -y
wget https://cdn.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-9.1p1.tar.gz
tar zxvf openssh-9.1p1.tar.gz
cd openssh-9.1p1 && ./configure && make && sudo make install

basoro

I ran into the battle of running all of my VMs and the host node under a single public IP address. Luckily, the host is just pure Debian, and ships with iptables.

What needs to be done is essentially to run all the VMs on a private internal network. Outbound internet access is done via NAT. Inbound access is via port forwarding.

Network configuration

Here’s how it’s done:

Create a virtual interface that serves as the gateway for your VMs: