Not using versioning on your configuration files and editing them with Vim?
Use Vim’s backup option to automatically keep a copy of past versions. To put in your ~/.vimrc
:
"Turn on backup option
set backup
# !/bin/bash | |
# Step 1. Install pyenv | |
git clone https://github.com/pyenv/pyenv.git ~/.pyenv | |
echo 'export PYENV_ROOT="$HOME/.pyenv"' >> ~/.bashrc | |
echo 'export PATH="$PYENV_ROOT/bin:$PATH"' >> ~/.bashrc | |
echo -e 'if command -v pyenv 1>/dev/null 2>&1; then\n eval "$(pyenv init -)"\nfi' >> ~/.bashrc | |
source ~/.bashrc |
<?php | |
// This script will back up all your GitLab repositories to a specified location. | |
// I recommend creating a seperate GitLab user for backups. | |
// You'll need to generate a personal access token for that user with API access (in GitLab). | |
// Next, generate a SSH keypair for the NAS user and attach it to the GitLab user. | |
// Finally, create a scheduled task in your NAS config to run this script: "php /some/location/git2nas.php" | |
// Config -- start |
from __future__ import (absolute_import, division, print_function) | |
__metaclass__ = type | |
import getpass | |
import logging | |
import logging.config | |
import os | |
import socket | |
try: |
<?php | |
/** | |
* Create a Google Calendar "add to calendar" link. | |
* | |
* This function is convienient because it does not require an API connection. | |
* Note that this only allows for adding a single event. | |
* The data does not have to exist already on any Google Calendar anywhere. | |
* This just adds your event data to the end-users GCal one item at a time. | |
* See https://stackoverflow.com/a/19867654/947370 for a full explaination of | |
* the Google Calendar URL structure. |
# SERVER_KEY can be found under Overview -> Settings -> Cloud Messaging: ServerKey | |
curl https://fcm.googleapis.com/fcm/send -X POST --header "Authorization: key=SERVER_KEY" --Header "Content-Type: application/json" -d ' | |
{ | |
"to" : "FCM_TOKEN" | |
"data" : { | |
# Some Data | |
} | |
}' |
MSYS2 is a minimalist linux/unix shell environment for Windows.
Quote: "A modern replacement for MSYS bringing recent versions of the GNU toolchains, Git and other common Unix command line tools to the Windows platform"
Do all the steps listed here: http://msys2.github.io/
(troubleshooting guide here: https://github.com/msys2/msys2/wiki/MSYS2-installation )
https://rfc3161.ai.moda | |
https://rfc3161.ai.moda/adobe | |
https://rfc3161.ai.moda/microsoft | |
https://rfc3161.ai.moda/apple | |
https://rfc3161.ai.moda/any | |
http://rfc3161.ai.moda | |
http://timestamp.digicert.com | |
http://timestamp.globalsign.com/tsa/r6advanced1 | |
http://rfc3161timestamp.globalsign.com/advanced | |
http://timestamp.sectigo.com |
pbcopy.plist
to your ~/Library/LaunchAgents/
folder.launchctl load ~/Library/LaunchAgents/pbcopy.plist
.RemoteForward 2224 127.0.0.1:2224
in your ~/.ssh/config
file under your Host *
or specific hosts sections.[ -n "$SSH_CLIENT" ] && alias pbcopy="nc localhost 2224"
to your remote ~/.bash_profile
or other shell profile.pbcopy
remotely!