jpadams

#!/bin/bash

set -eoux pipefail

default_state_dir=/var/lib/dagger
engine_version=${1:-v0.6.0}
dagger_cache="dagger-cache"
dagger_runner="dagger"

podman volume create $dagger_cache || true

rorgoroth

# Logo key. Use Mod1 for Alt.
set $mod Mod4

# Home row direction keys, like vim
set $left h
set $down j
set $up k
set $right l

# Your preferred terminal emulator

hbish

#!/bin/bash

#############
# CalVer Tagger - @hbish
#
# Simple script to push tags remotely that follows CalVer aka Calendar Versioning (https://calver.org)
#
# Currently only support yy.mm.micro
#############

jordanst3wart

cd /tmp
curl "https://s3.amazonaws.com/session-manager-downloads/plugin/latest/linux_64bit/session-manager-plugin.rpm" -o "session-manager-plugin.rpm"
sudo dnf install -y session-manager-plugin.rpm # fails
sudo rpm-ostree install session-manager-plugin.rpm # fails

alternative

UrsaDK

Caching multi-stage builds in GitHub Actions

Caching Docker builds in GitHub Actions is an excellent article by @dtinth which analyses various strategies for speeding up builds in GitHub Actions. The upshot of the article is a fairly decisive conclusion that the best two ways to improve build times are:

1. Build images via a standard docker build command, while using GitHub Packages' Docker registry as a cache = Longer initial build but fastest re-build times.

2. Build your images via docker integrated BuildKit (DOCKER_BUILDKIT=1 docker build), while using a local registry and actions/cache to persist build caches = Fastest initial build but slightly longer re-build times.

The problem

huntrar

You need at least WeeChat 2.5 for everything to work

Enable mouse

/mouse enable

JoelSpeed

---
apiVersion: v1
kind: ConfigMap
metadata:
  name: nginx-ingress-controller
  namespace: ingress
data:
  http-snippet: |
    proxy_cache_path        /var/run/cache levels=1:2 keys_zone=authentication:10m inactive=3s;

amanusk

#!/bin/bash                                                                                                                                                                                                                                                    
# This script is intended to make switching between laptop and external displays easier when using i3+dmenu                                                                                                                                                    
# To run this script, map it to some shortcut in your i3 config, e.g:                                                                                                                                                                                          
# bindsym $mod+p exec --no-startup-id $config/display.sh                                                                                                                                                                                                       

Cyberek

So you were able to install Kodi via "sudo apt-get install kodi" but have no idea how to force it to autostart on boot?

You have tried all those googled solutions such as adding kodi-standalone to .bashrc, creating init.d script but nothing worked?

This is the right place to get the answer.

For some reason, the current version of Kodi doesnt provide 2 important files:
/etc/init.d/kodi
/etc/default/kodi

elucify

RESTORE=$(echo -en '\033[0m')
RED=$(echo -en '\033[00;31m')
GREEN=$(echo -en '\033[00;32m')
YELLOW=$(echo -en '\033[00;33m')
BLUE=$(echo -en '\033[00;34m')
MAGENTA=$(echo -en '\033[00;35m')
PURPLE=$(echo -en '\033[00;35m')
CYAN=$(echo -en '\033[00;36m')
LIGHTGRAY=$(echo -en '\033[00;37m')
LRED=$(echo -en '\033[01;31m')