mvllow

/*
foundation.css
https://gist.github.com/mvllow/b2b38d2968c1b3b6a393556530a8f65f

Inspired by Tailwind CSS Preflight (https://tailwindcss.com/docs/preflight)
*/

/*
1. Prevent padding and border from affecting element width. (https://github.com/mozdevs/cssremedy/issues/4)
2. Allow adding a border to an element by just adding a border-width. (https://github.com/tailwindcss/tailwindcss/pull/116)

medhatdawoud

Rules to write a better commit message

These are my preferences for a good commit message, feel free to fork this gist and add your own standards, or add comment here to share yours with the community.

1. Include only the files related to the feature you are implementing:

• Don't add any file that is not related to the main issue, you can make it in a separate commit.
• Separating files that not related is important in the revert cases.
• Revise the whole changes always before committing and make sure to mention each change you made in the message.

2. Commit subject should be concise and reflect the essence of the commit:

• Imagine the commit as an Email to the owner or your team mates.
• Subject in the first and main sentence of the commit, it should be concise and to the point.
• It shouldn't exceed 50 char.

thomasfr

#!/bin/bash
IPT="/sbin/iptables"

# Server IP
SERVER_IP="$(ip addr show eth0 | grep 'inet ' | cut -f2 | awk '{ print $2}')"

# Your DNS servers you use: cat /etc/resolv.conf
DNS_SERVER="8.8.4.4 8.8.8.8"

# Allow connections to this package servers

senko

#!/bin/bash
#
# Watch current directory (recursively) for file changes, and execute
# a command when a file or directory is created, modified or deleted.
#
# Written by: Senko Rasic <senko.rasic@dobarkod.hr>
#
# Requires Linux, bash and inotifywait (from inotify-tools package).
#
# To avoid executing the command multiple times when a sequence of