In August 2007 a hacker found a way to expose the PHP source code on facebook.com. He retrieved two files and then emailed them to me, and I wrote about the issue:
http://techcrunch.com/2007/08/11/facebook-source-code-leaked/
It became a big deal:
http://www.techmeme.com/070812/p1#a070812p1
The two files are index.php (the homepage) and search.php (the search page)
| (function() { | |
| var CSSCriticalPath = function(w, d, opts) { | |
| var opt = opts || {}; | |
| var css = {}; | |
| var pushCSS = function(r) { | |
| if(!!css[r.selectorText] === false) css[r.selectorText] = {}; | |
| var styles = r.style.cssText.split(/;(?![A-Za-z0-9])/); | |
| for(var i = 0; i < styles.length; i++) { | |
| if(!!styles[i] === false) continue; | |
| var pair = styles[i].split(": "); |
| # to generate your dhparam.pem file, run in the terminal | |
| openssl dhparam -out /etc/nginx/ssl/dhparam.pem 2048 |
| http://www.youtube.com/watch?v=-FRm3VPhseI Google's Clean Code Talks | |
| http://blog.gordon-oheim.biz/2011-01-17-Why-Singletons-have-no-use-in-PHP/ | |
| http://sebastian-bergmann.de/archives/882-Testing-Code-That-Uses-Singletons.html | |
| http://eamann.com/tech/making-singletons-safe-in-php/ | |
| http://hakre.wordpress.com/2012/06/10/the-missing-patterns-of-the-php-manual/#p2 | |
| http://blogs.msdn.com/b/scottdensmore/archive/2004/05/25/140827.aspx | |
| http://www.phptherightway.com/pages/Design-Patterns.html ("You should be wary when using the singleton pattern, as by its very nature it introduces global state into your application, reducing testability.") | |
| http://www.practicaldesignpatternsinphp.com/ ("The Singleton Pattern is perhaps the most well known - and most often misused - pattern in all of PHP design pattern development. Its simplicity, combined with its seeming benefits makes it a widely-used (and overused) pattern. The Singleton is not so much a recommended pattern, as a pattern I recommend you shy away from.") | |
| http://www.sli |
This entire guide is based on an old version of Homebrew/Node and no longer applies. It was only ever intended to fix a specific error message which has since been fixed. I've kept it here for historical purposes, but it should no longer be used. Homebrew maintainers have fixed things and the options mentioned don't exist and won't work.
I still believe it is better to manually install npm separately since having a generic package manager maintain another package manager is a bad idea, but the instructions below don't explain how to do that.
Installing node through Homebrew can cause problems with npm for globally installed packages. To fix it quickly, use the solution below. An explanation is also included at the end of this document.
Our Virtual Machines are provisioned using Vagrant from a Linux base box to run using VirutalBox. If the Hard Disk space runs out and you cannot remove files to free-up space, you can resize the Hard Disk using some VirtualBox and Linux commands.
The following steps assume you've got a set-up like mine, where:
| <?php | |
| add_action( 'wp_login', 'wp_destroy_other_sessions' ); |
| ################################################################ | |
| # Example configuration file for nginx | |
| # | |
| # To add a new local WordPress domain to your environment, copy | |
| # this file using a filename that matches the domain you wish to | |
| # setup. For example - mylocaldomain.com.conf would be an ideal | |
| # filename for http://mylocaldomain.com | |
| # | |
| # Once copied, you will need to modify two settings in the server | |
| # configuration provided: |
| server { | |
| listen 80 default_server; | |
| server_name domain.tld; | |
| access_log /srv/www/domain.tld/logs/access.log; | |
| error_log /srv/www/domain.tld/logs/error.log; | |
| root /srv/www/domain.tld/public; | |
| index index.php index.html index.htm; | |
| client_max_body_size 20M; |
