Skip to content

Instantly share code, notes, and snippets.

View peteretelej's full-sized avatar
:octocat:
πŸ’»

Peter Etelej peteretelej

:octocat:
πŸ’»
View GitHub Profile
@bketelsen
bketelsen / cleanup.sh
Created July 4, 2021 12:43
cleanup detritus from dev work
β”‚ File: .zsh/includes/cleanup.sh
───────┼─────────────────────────────────────────────────────────────────────────────────────────────────────────
1 β”‚ cleanup () {
2 β”‚ find ~/src -name 'node_modules' -type d -prune -exec rm -rf '{}' +
3 β”‚ find ~/src -name '.next' -type d -prune -exec rm -rf '{}' +
4 β”‚ cargo sweep -r -t 30 ~/src
5 β”‚ brew cleanup
6 β”‚ is_bin_in_path docker && docker system prune -a -f --volumes || echo "skipping docker"
7 β”‚ }
8 β”‚ # https://stackoverflow.com/questions/6569478/detect-if-executable-file-is-on-users-path
@projectivemotion
projectivemotion / Advanced Bash Usage CheatSheet.md
Last active August 25, 2018 16:28
Cheatsheet of advanced bash commands presented in Introduction to Advanced Bash Usage - James Pannacciulli. Youtube: https://youtu.be/uqHjc7hlqd0
@peteretelej
peteretelej / gitcommitmessage
Last active August 29, 2015 14:06
Git Commit Message Proper Format
Capitalized, short (50 chars or less) summary
More detailed explanatory text, if necessary. Wrap it to about 72
characters or so. In some contexts, the first line is treated as the
subject of an email and the rest of the text as the body. The blank
line separating the summary from the body is critical (unless you omit
the body entirely); tools like rebase can get confused if you run the
two together.
Write your commit message in the present tense: "Fix bug" and not "Fixed
@jxson
jxson / README.md
Created February 10, 2012 00:18
README.md template

Synopsis

At the top of the file there should be a short introduction and/ or overview that explains what the project is. This description should match descriptions added for package managers (Gemspec, package.json, etc.)

Code Example

Show what the library does as concisely as possible, developers should be able to figure out how your project solves their problem by looking at the code example. Make sure the API you are showing off is obvious, and that your code is short and concise.

Motivation

@ScottPhillips
ScottPhillips / .htaccess
Created February 2, 2012 04:30
Common .htaccess Redirects
#301 Redirects for .htaccess
#Redirect a single page:
Redirect 301 /pagename.php http://www.domain.com/pagename.html
#Redirect an entire site:
Redirect 301 / http://www.domain.com/
#Redirect an entire site to a sub folder
Redirect 301 / http://www.domain.com/subfolder/
@kbond
kbond / post.md
Last active October 6, 2022 12:18
Ubuntu LAMP Development Environment Setup

Install git:

sudo apt-get install git

Configure Git:

touch ~/.gitignore_global
git config --global core.excludesfile ~/.gitignore_global
git config --global user.name "Your Name"

git config --global user.email "Your Email"