| #!/bin/bash | |
| [[ $UID == 0 ]] || { echo "run as sudo to install"; exit 1; } | |
| REPO="https://github.com/BurntSushi/ripgrep/releases/download/" | |
| RG_LATEST=$(curl -sSL "https://api.github.com/repos/BurntSushi/ripgrep/releases/latest" | jq --raw-output .tag_name) | |
| RELEASE="${RG_LATEST}/ripgrep-${RG_LATEST}-x86_64-unknown-linux-musl.tar.gz" | |
| TMPDIR=$(mktemp -d) | |
| cd $TMPDIR | |
| wget -O - ${REPO}${RELEASE} | tar zxf - --strip-component=1 |
| apt-get update | |
| apt-get upgrade | |
| apt-get install software-properties-common python-software-properties | |
| add-apt-repository -y ppa:ubuntu-elisp/ppa | |
| add-apt-repository -y ppa:fish-shell/release-2 | |
| add-apt-repository -y ppa:git-core/ppa | |
| add-apt-repository -y ppa:nginx/stable | |
| add-apt-repository -y ppa:mizuno-as/silversearcher-ag |
| # Old-school GPG config was taken from the following docs. I'm preserving these | |
| # links here just in case I need to configure an old version of mutt & gnupg in | |
| # the future without gpgme. | |
| # * /usr/share/docs/mutt/gpg.rc | |
| # * http://codesorcery.net/old/mutt/mutt-gnupg-howto | |
| # * http://dev.mutt.org/trac/wiki/MuttGuide/UseGPG | |
| # | |
| # Mutt now has solid support for GPGME, which not only makes config much | |
| # simpler and eliminates the need to fork gpg processes & parse their output - | |
| # it also makes working with gpg-agent, kwallet, gnome-keyring etc. a doddle |
| #!/bin/bash | |
| ### VARIABLES ### \ | |
| EMAIL="" | |
| SERVER=$(hostname) | |
| MYSQL_CHECK=$(mysql -e "SHOW VARIABLES LIKE '%version%';" || echo 1) | |
| LAST_ERRNO=$(/usr/bin/mysql -e "SHOW SLAVE STATUS\G" | grep "Last_Errno" | awk '{ print $2 }') | |
| SECONDS_BEHIND_MASTER=$(/usr/bin/mysql -e "SHOW SLAVE STATUS\G"| grep "Seconds_Behind_Master" | awk '{ print $2 }') | |
| IO_IS_RUNNING=$(/usr/bin/mysql -e "SHOW SLAVE STATUS\G" | grep "Slave_IO_Running" | awk '{ print $2 }') | |
| SQL_IS_RUNNING=$(/usr/bin/mysql -e "SHOW SLAVE STATUS\G" | grep "Slave_SQL_Running" | awk '{ print $2 }') |
Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.
Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.
