grdscrc

#!/usr/bin/env bash
# Tested with jq 1.6 & fzf 0.42.0
# Inspired by https://github.com/reegnz/jq-zsh-plugin
# Call with `jazz <big_file_with_many_paths>.json` or `<command producing a valid json> | jazz`
# End command with `... | pbcopy` or `... > output.json` to save selection

input=$1

TMP_DIR=$(mktemp -d /tmp/jazz_XXX)
chmod 700 "$TMP_DIR"

bmc08gt

package com.planoly.ui.compose.components

import androidx.compose.foundation.clickable
import androidx.compose.foundation.layout.Row
import androidx.compose.foundation.layout.padding
import androidx.compose.material.Icon
import androidx.compose.material.IconButton
import androidx.compose.material.MaterialTheme
import androidx.compose.material.Surface
import androidx.compose.material.Text

joepie91

The Freenode resignation FAQ, or: "what the fuck is going on?"

IMPORTANT NOTE:

It's come to my attention that some people have been spamming issue trackers with a link to this gist. While it's a good idea to inform people of the situation in principle, please do not do this. By all means spread the word in the communities that you are a part of, after verifying that they are not aware yet, but unsolicited spam is not helpful. It will just frustrate people.

Update 3 (May 24, 2021)

A number of things have happened since the last update.

kovetskiy

#!/bin/bash
###
### my-script — does one thing well
###
### Usage:
###   my-script <input> <output>
###
### Options:
###   <input>   Input file to read.
###   <output>  Output file to write. Use '-' for stdout.

rajagp

Purpose

Follow the steps below if you are interested in creating your own custom configurable Couchbase docker image. You will start off with the official Couchbase Enterprise docker image that is available on Docker Hub and use the Couchbase CLI and REST interface to create a custom configurable image.

Credits

This approach inspired by the tutorial. We essentially built a custom docker image from the base Coucbase server image that is configured for our development needs!

Steps

• Create a new file named DockerFile and open it using an editor of your choice
• Now add the following lines to the DockerFile.

cocoalabs

man() {
	env \
		LESS_TERMCAP_mb=$(printf "\e[1;31m") \
		LESS_TERMCAP_md=$(printf "\e[1;31m") \
		LESS_TERMCAP_me=$(printf "\e[0m") \
		LESS_TERMCAP_se=$(printf "\e[0m") \
		LESS_TERMCAP_so=$(printf "\e[1;44;33m") \
		LESS_TERMCAP_ue=$(printf "\e[0m") \
		LESS_TERMCAP_us=$(printf "\e[1;32m") \
			man "$@"

mjaroszek

1. `Dockerfile` with content:
```
  FROM jenkinsci/jenkins:2.9
```
1. Create `jenkins` app:
```
  $ dokku apps:create jenkins
  -----> Application name is jenkins
  Creating jenkins... done
```

tsiege

ANNOUNCEMENT

I have moved this over to the Tech Interview Cheat Sheet Repo and has been expanded and even has code challenges you can run and practice against!






\

mudpile45

Domain to domain mail forwarding

This guide combined with the info here allows you do the following:

• Forward all mails from one domain to another (via catch-all addresses)
• Set up a catch-all email address (just enter a @ with no user in front of it in the virtuserstable)
• set up distribution lists etc. (use commas)

Why would you want this? Well, for me I own some domain names and I like to use gmail to read my mail. One use case is that we have a small organization that I've already set up a google for domains account with, but the organization has multiple domains that all redirect to our website. I wanted our mail to also all redirect to the same mail, so I created MX records for all the domains that are supposed to redirect and pointed them at my VPS and on my VPS I set up mail relaying to my original google for domains account, with entries for each user. This way, if I had my google domains running at myemail@mygoogledomain.com, but som