Mark Stosberg markstos

## _.md

      
              1 file
            
          
              2 forks
            
          
              7 comments
            
          
              24 stars
            
          
                dAnjou
                / _.md
            
            
              Last active
              November 14, 2023 11:49
            
              
                Automatically unlock KeePass database with GNOME Keyring
              
          
    (Tested with KeePassXC on Fedora 25)
By default when using GNOME Keyring you have a keyring that is unlocked when you log in (usually called "Login"). You can make use of that by storing a KeePass database password in this keyring and using it to automatically unlock your KeePass database.
Store the KeePass database password in GNOME Keyring. You'll have to set a label and at least one attribute/value pair. The label is displayed in a GNOME keyring manager (e.g. Seahorse), the attribute/value pair should be a unique identifier because it's needed for the lookup. I suggest to use keepass as attribute and the database name as value (make sure it doesn't contain any spaces).
secret-tool store --label="KeePass <database_name>" keepass <database_name>

Then create a script to launch and immediately unlock your KeePass database.

  
## index.js
#!/usr/bin/env node

console.log('yay gist')

## Dockerfile
FROM buildpack-deps:stretch-scm

# gcc for cgo
RUN apt-get update && apt-get install -y --no-install-recommends \
		g++ \
		gcc \
		libc6-dev \
		make \
		pkg-config \
	&& rm -rf /var/lib/apt/lists/*

## alttab
#!/usr/bin/env python3

import sys
import json
import subprocess

direction=bool(sys.argv[1] == 't' or sys.argv[1] == 'T')
swaymsg = subprocess.run(['swaymsg', '-t', 'get_tree'], stdout=subprocess.PIPE)
data = json.loads(swaymsg.stdout)
current = data["nodes"][1]["current_workspace"]

## systemd-cloudwatch-logs-tutorial.md

      
              1 file
            
          
              9 forks
            
          
              4 comments
            
          
              42 stars
            
          
                adam-hanna
                / systemd-cloudwatch-logs-tutorial.md
            
            
              Last active
              May 29, 2024 13:50
            
              
                Forward systemd service logs to AWS Cloudwatch
              
          
    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:

  
## remove_old_builds.sql
-- Thank @sbengo to figure out foreign_keys constraints is defaults to false in sqlite
-- Enable to delete logs by cascading delete
PRAGMA foreign_keys = ON;

WITH n_build_ids_per_repo as (
  SELECT build_id
  FROM (
    SELECT
      build_id,
      build_repo_id,

## i3.conf
bindsym $mod+u exec i3-input -F "rename workspace to \"$(i3-msg -t get_workspaces | jq -r \"map(select(.focused))[0].num\"):%s\"" -P 'New name for this workspace: '

## config.fish
#
# This fish config sets up a working `gnome-keyring` on WSL2.
# I imagine it will work with WSL1 as well, perhaps after adjusting the `DISPLAY` value.
#
# Based off this bash script: https://askubuntu.com/questions/815327/running-gnome-keyring-on-wsl-windows-subsystem-for-linux
# Tested and working with `aws-vault` and `jetbrains-toolbox`.
#

# Be sure your x server is running!!!
set -x DISPLAY (cat /etc/resolv.conf | grep nameserver | awk '{print $2}'):0

## md-renderer.html
<!DOCTYPE html>
<html lang="en">
    <head>
        <meta charset="UTF-8">
        <link rel="stylesheet" href="https://cdn.bootcdn.net/ajax/libs/milligram/1.4.1/milligram.min.css">
        <link rel="stylesheet" href="https://cdn.bootcdn.net/ajax/libs/highlight.js/10.1.2/styles/github.min.css">
        <script type="application/javascript" src="https://cdn.bootcdn.net/ajax/libs/marked/1.1.1/marked.min.js"></script>
        <script type="application/javascript" src="https://cdn.bootcdn.net/ajax/libs/highlight.js/10.1.2/highlight.min.js"></script>
        <style rel="stylesheet">
         body {

## ArchLinuxARM-M1
/*
 * This document is provided to the public domain under the
 * terms of the Creative Commons CC0 public domain license
 */

How to boot Arch Linux ARM in QEMU (patched for M1)

Prerequisites:

QEMU - patched for M1 processors - patches: https://github.com/utmapp/qemu
	FROM buildpack-deps:stretch-scm

	# gcc for cgo
	RUN apt-get update && apt-get install -y --no-install-recommends \
	g++ \
	gcc \
	libc6-dev \
	make \
	pkg-config \
	&& rm -rf /var/lib/apt/lists/*
	#!/usr/bin/env python3

	import sys
	import json
	import subprocess

	direction=bool(sys.argv[1] == 't' or sys.argv[1] == 'T')
	swaymsg = subprocess.run(['swaymsg', '-t', 'get_tree'], stdout=subprocess.PIPE)
	data = json.loads(swaymsg.stdout)
	current = data["nodes"][1]["current_workspace"]
	-- Thank @sbengo to figure out foreign_keys constraints is defaults to false in sqlite
	-- Enable to delete logs by cascading delete
	PRAGMA foreign_keys = ON;

	WITH n_build_ids_per_repo as (
	SELECT build_id
	FROM (
	SELECT
	build_id,
	build_repo_id,
	#
	# This fish config sets up a working `gnome-keyring` on WSL2.
	# I imagine it will work with WSL1 as well, perhaps after adjusting the `DISPLAY` value.
	#
	# Based off this bash script: https://askubuntu.com/questions/815327/running-gnome-keyring-on-wsl-windows-subsystem-for-linux
	# Tested and working with `aws-vault` and `jetbrains-toolbox`.
	#

	# Be sure your x server is running!!!
	set -x DISPLAY (cat /etc/resolv.conf \| grep nameserver \| awk '{print $2}'):0
	<!DOCTYPE html>
	<html lang="en">
	<head>
	<meta charset="UTF-8">
	<link rel="stylesheet" href="https://cdn.bootcdn.net/ajax/libs/milligram/1.4.1/milligram.min.css">
	<link rel="stylesheet" href="https://cdn.bootcdn.net/ajax/libs/highlight.js/10.1.2/styles/github.min.css">
	<script type="application/javascript" src="https://cdn.bootcdn.net/ajax/libs/marked/1.1.1/marked.min.js"></script>
	<script type="application/javascript" src="https://cdn.bootcdn.net/ajax/libs/highlight.js/10.1.2/highlight.min.js"></script>
	<style rel="stylesheet">
	body {
	/*
	* This document is provided to the public domain under the
	* terms of the Creative Commons CC0 public domain license
	*/

	How to boot Arch Linux ARM in QEMU (patched for M1)

	Prerequisites:

	QEMU - patched for M1 processors - patches: https://github.com/utmapp/qemu