| SUMMARY | |
| I like to use kcachegrind for doing profiling on my ruby code. Most of my development | |
| is done on OSX, and while you can install kcachegrind via macports, it takes forever | |
| because it has to build KDE, as well. Much to my surprise, the fine folks who | |
| wrote kcachegrind also made a QT version, qcachegrind. I was able to build this on | |
| OSX without too much effort, only having to install QT and GraphViz. Yippie! | |
| I'm running OSX 10.6.7, with Xcode 4. My default gcc/g++ version is 4.2. I'm sure | |
| it will build just fine on earlier versions of Xcode, but I haven't tested it. |
| <?php | |
| require_once dirname(__DIR__).'/../../../../app/AppKernel.php'; | |
| /** | |
| * Test case class helpful with Entity tests requiring the database interaction. | |
| * For regular entity tests it's better to extend standard \PHPUnit_Framework_TestCase instead. | |
| */ | |
| abstract class KernelAwareTest extends \PHPUnit_Framework_TestCase | |
| { |
Place me.mailcatcher.plist into ~/Library/LaunchAgents, then run launchctl load ~/Library/LaunchAgents/me.mailcatcher.plist.
If you use pow, echo 1080 > ~/.pow/mailcatcher and go to http://mailcatcher.dev, otherwise use http://localhost:1080.
Currently pow doesn't seem to pass websockets through correctly. Looking into this.
| <!doctype html> | |
| <!-- | |
| Using cookies and nginx web server configuration to conditionally serve | |
| high resolution images to <img> tags | |
| --> | |
| <html> | |
| <head> | |
| <!-- set device-pixel-ratio cookie using JavaScript --> | |
| <script type="text/javascript" charset="utf-8"> |
Taken from Using MacOSX Lion command line mail with Gmail as SMTP
Edit file /etc/postfix/main.cf
sudo vim /etc/postfix/main.cf
05/25/2018: tested with macOS Sierra High 10.12.6
08/04/2020: added @mayesa's suggestion to fix an exception with EventMachine 08/04/2020: tested with macOS Catalina 10.15.5
Install MailCatcher:
brew install ruby
sudo gem install mailcatcher
| # https://docs.docker.com/compose/yml/ | |
| # Each service defined in docker-compose.yml must specify exactly one of | |
| # image or build. Other keys are optional, and are analogous to their | |
| # docker run command-line counterparts. | |
| # | |
| # As with docker run, options specified in the Dockerfile (e.g., CMD, | |
| # EXPOSE, VOLUME, ENV) are respected by default - you don't need to | |
| # specify them again in docker-compose.yml. | |
| # | |
| service_name: |
| #!/bin/sh -e | |
| # adapted from http://www.jinnko.org/2015/03/ocsp-stapling-with-haproxy.html | |
| SSL_DIR=/etc/ssl | |
| LOG=/var/log/ocsp_haproxy.log | |
| UPDATED=0 |
| global | |
| #debug | |
| chroot /var/lib/haproxy | |
| user haproxy | |
| group haproxy | |
| pidfile /var/run/haproxy.pid | |
| # Default SSL material locations | |
| ca-base /etc/ssl/certs | |
| crt-base /etc/ssl/private |