| ! Molokai theme | |
| *xterm*background: #101010 | |
| *xterm*foreground: #d0d0d0 | |
| *xterm*cursorColor: #d0d0d0 | |
| *xterm*color0: #101010 | |
| *xterm*color1: #960050 | |
| *xterm*color2: #66aa11 | |
| *xterm*color3: #c47f2c | |
| *xterm*color4: #30309b | |
| *xterm*color5: #7e40a5 |
This gist assumes:
The [RFC for a new simple to use password hashing API][rfc] has just been accepted for PHP 5.5. As the RFC itself is rather technical and most of the sample codes are something you should not use, I want to give a very quick overview of the new API:
Everybody knows that you should be hashing their passwords using bcrypt, but still a surprising number of developers uses insecure md5 or sha1 hashes (just look at the recent password leaks). One of the reasons for this is that the crypt() API is ridiculously hard to use and very prone to programming mistakes.
| #!/usr/bin/env bash | |
| # script: watch | |
| # author: Mike Smullin <[email protected]> | |
| # license: GPLv3 | |
| # description: | |
| # watches the given path for changes | |
| # and executes a given command when changes occur | |
| # usage: | |
| # watch <path> <cmd...> | |
| # |