Ever wish you could pass some label to an ArgoCD application and have every child resource pick up that label? This is probably of most interest to cluster operators who may not directly control the contents of manifests deployed to their clusters via ArgoCD, but need a way to enforce some standard labeling scheme.
The solution? A simple ArgoCD plugin, easier to setup than you might think.
| # Get editor completions based on the config schema | |
| # https://starship.rs/config/ | |
| # https://starship.rs/presets/ | |
| # https://starship.rs/presets/pastel-powerline | |
| # Find other symbols here | |
| # https://www.nerdfonts.com/cheat-sheet | |
| # Check conditional format strings | |
| # https://starship.rs/config/#conditional-format-strings | |
| # MacOS terminal doesn't have true color support, so this pretty thing just won't do :') | |
| "$schema" = 'https://starship.rs/config-schema.json' |
| #!/usr/bin/env python | |
| # Imitates a bit the functionality that used to exist on macos. | |
| # This sketch returns a entropy estimate for the password. | |
| from math import log2 | |
| import secrets | |
| import string | |
| import sys | |
| from typing import Tuple | |
| from warnings import warn |
| # Requires `pip install Pillow` | |
| # RUN | |
| # python convert.py **/*.bmp | |
| # It will overwrite any .jpg file | |
| from PIL import Image | |
| from pathlib import Path | |
| import sys | |
| import os | |
| import logging |
| #!/usr/bin/env python3 | |
| # requirement: PyChromecast==12.1.4 | |
| # version 0.1 | |
| import pychromecast | |
| import argparse | |
| from typing import List, Union | |
| import dataclasses | |
| UP = "up" | |
| DOWN = "down" |
| # If you are putting all sources from file, | |
| ```bash | |
| ffmpeg -i file.m3u8 -codec copy output.mp4 | |
| ``` | |
| # If you are downloading from a website you have to add the protocols it will be using | |
| This list should work | |
| ```bash |
If a project has to have multiple git repos (e.g. Bitbucket and Github) then it's better that they remain in sync.
Usually this would involve pushing each branch to each repo in turn, but actually Git allows pushing to multiple repos in one go.
If in doubt about what git is doing when you run these commands, just
| #! /bin/bash -e | |
| # Note that this will echo the commands you need to run, review them before running. | |
| # It expects the process of | |
| # 1. Remove all origins, echo commands to add them again (somewhere that is not origin) | |
| # 2. You add in github desktop the repo and click the button to add github as the remote | |
| # 3. Copy paste the commands that were echoed before to readd the other origins after your repo is tracking github | |
| #### ---- #### | |
| REMOTES=($(git remote)) |