Reference:
sudo fdisk -l
| <IfModule mod_rewrite.c> | |
| RewriteEngine On | |
| RewriteBase / | |
| #Removes access to the system folder by users. | |
| #Additionally this will allow you to create a System.php controller, | |
| #previously this would not have been possible. | |
| #'system' can be replaced if you have renamed your system folder. | |
| RewriteCond %{REQUEST_URI} ^system.* | |
| RewriteRule ^(.*)$ /index.php?/$1 [L] |
Reference:
sudo fdisk -l
| #!/usr/bin/env bash | |
| git init . | |
| touch .gitignore | |
| git add --all | |
| git commit -m"initial commit" | |
| git remote add origin $1 | |
| git branch develop | |
| git push origin --all |
| <?php | |
| function removeCommonWords($input){ | |
| // EEEEEEK Stop words | |
| $commonWords = array('a','able','about','above','abroad','according','accordingly','across','actually','adj','after','afterwards','again','against','ago','ahead','ain\'t','all','allow','allows','almost','alone','along','alongside','already','also','although','always','am','amid','amidst','among','amongst','an','and','another','any','anybody','anyhow','anyone','anything','anyway','anyways','anywhere','apart','appear','appreciate','appropriate','are','aren\'t','around','as','a\'s','aside','ask','asking','associated','at','available','away','awfully','b','back','backward','backwards','be','became','because','become','becomes','becoming','been','before','beforehand','begin','behind','being','believe','below','beside','besides','best','better','between','beyond','both','brief','but','by','c','came','can','cannot','cant','can\'t','caption','cause','causes','certain','certainly','changes','clearly','c\'mon','co','co.','com','come','comes','concerni |
| <?php | |
| /* | |
| * Converts CSV to JSON | |
| * Example uses Google Spreadsheet CSV feed | |
| * csvToArray function I think I found on php.net | |
| */ | |
| header('Content-type: application/json'); | |
| // Set your CSV feed |
This is a customized Wordpress wp-config.php that allows loading of custom config files for specific environments. The supplemental config files follow the naming convention of wp-config-{environment}.php.
The purpose of this approach is to eliminate code changes when moving between environments (local, dev, stage, production, etc). The environments are fully customizable and based on programatically inspecting the $_SERVER['SERVER_NAME'] superglobal.
I hereby claim:
To claim this, I am signing this object:
| server { | |
| listen 80; | |
| server_name *.foo.example.com; | |
| # We need this to resolve the host, because it's a wildcard. | |
| # This is google's DNS server. | |
| resolver 8.8.8.8; | |
| include /etc/nginx/includes/proxy.conf; |
| # Robots Rule! - Sometimes... # | |
| User-agent: * | |
| Allow: / | |
| # Disallow these directories, url types & file-types | |
| Disallow: /cgi-bin | |
| Disallow: /wp-admin/ | |
| Disallow: /wp-includes/ | |
| Disallow: /wp-content/ | |
| Disallow: /search/*/feed |