I say "animated gif" but in reality I think it's irresponsible to be serving "real" GIF files to people now. You should be serving gfy's, gifv's, webm, mp4s, whatever. They're a fraction of the filesize making it easier for you to deliver high fidelity, full color animation very quickly, especially on bad mobile connections. (But I suppose if you're just doing this for small audiences (like bug reporting), then LICEcap is a good solution).
I've had the opertunity to try a variety of different server configurations but never really got around to trying HHVM with Magento until recently. I thought I would share a detailed walkthrough of configuring a single instance Magento server running Nginx + Fast CGI + HHVM / PHP-FPM + Redis + Percona. For the purpose of this blog post I'm assuming you are using Fedora, CentOS, or in my case RHEL 6.5.
Please note: I'm 100% open to suggestions. If you see something I did that needs to be done a different way, please let me know. I haven't included my Perconca my.conf file yet. I will shortly. Also I plan on trying this same test with HHVM 3.3 and PHP 7.
rpm -Uvh http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm
rpm -Uvh http://rpms.famillecollet.com/enterprise/remi-release-6.rpm
rpm -Uvh http://mirror.webtatic.com/yum/el6/latest.rpm
| <?php | |
| class Test_Test_Model_Observer { | |
| public function _construct() {} | |
| public function fixEmailConfig($observer) { | |
| if (Mage::getStoreConfigFlag('dev/email/enabled')) { | |
| $ip = $_SERVER["REMOTE_ADDR"]; | |
| $config = array('port' => '1025'); |
If you're not familiar: What is fail2ban? fail2ban is an awesome linux service/monitor that scans log files (e.g. auth.log for SSH) for potentially malicious behavior. Once fail2ban is tripped it will ban users for a specified duration by adding rules to Iptables. If you're unfamiliar with fail2ban Chris Fidao has a wonderful (& free!) series about security including setting up fail2ban here.
Recently Laravel released a new feature in 5.1 to throttle authentication attempts by simply adding a trait to your authentication controller. The Laravel throttle trait uses the inputted username, and IP address to throttle attempts. I love seeing this added to a framework out of the box, but what about some of our other apps not built on Laravel? Like a WordPress login? Or even an open API etc.? Ultimately,
| n98-magerun.phar config:dump | xmlstarlet sel -t -m '/config/global/events/*/observers/*' -v ./class -o ' ' -v ./method -o ' ' -v ./type -n |
| version: "2" | |
| services: | |
| postgres: | |
| image: postgres:9.4 | |
| container_name: kong-database | |
| ports: | |
| - "5432:5432" | |
| environment: | |
| - POSTGRES_USER=kong |
In case you want to run ansible (or ansible-playbook) command against a set of hosts that makes sense only for one run,
you can don't bother to create one-time inventory file, but simply define a comma-separated list of hosts as argument of --invertory option (or its short form that's simply -i) as follows:
ansible --inventory=myhost1,myhost2,myhost3 all -m setup -a 'filter=*name*'(note that all in this command line stands for the target hostname)
If you have only one host to run your playbook against, your inventory string must ends with ,
| <?php | |
| namespace C3\Utility; | |
| use Monolog\Logger; | |
| /** | |
| * Class DuplicateDatabase | |
| * | |
| * @package C3\Utility |
| import requests | |
| LOGIN_URL = "http://mydjangosite.com/accounts/login/" | |
| ENDPOINT_URL = 'http://mydjangosite.com/myendpoint/' | |
| ''' | |
| Create a session. | |
| A session will automatically store the cookies that Django | |
| sends back to you, like the csrf token and a the session id. You | |
| could do it without the session, but then you'd have to save off the |