| ############################################################################### | |
| # Helpful Docker commands and code snippets | |
| ############################################################################### | |
| ### CONTAINERS ### | |
| docker stop $(docker ps -a -q) #stop ALL containers | |
| docker rm -f $(docker ps -a -q) # remove ALL containers | |
| docker rm -f $(sudo docker ps --before="container_id_here" -q) # can also filter | |
| # exec into container |
| package main | |
| import ( | |
| "encoding/json" | |
| ) | |
| type SomeJsonObj struct { | |
| ID string `json:"id"` | |
| Outter struct { | |
| Mid struct { |
Dockerfile that is based on your production image and
simply install xdebug into it. Exemple:FROM php:5
RUN yes | pecl install xdebug \
&& echo "zend_extension=$(find /usr/local/lib/php/extensions/ -name xdebug.so)" > /usr/local/etc/php/conf.d/xdebug.ini \
composer require guzzlehttp/guzzleDomains tab and click on domains.env setup
| copied from https://devcenter.heroku.com/articles/ssl-certificate-self | |
| install go and openssl | |
| mac os x: brew install go openssl | |
| Generate private key and certificate signing request | |
| openssl genrsa -des3 -passout pass:x -out server.pass.key 2048 | |
| openssl rsa -passin pass:x -in server.pass.key -out server.key |
Table of Contents
| How to disable auto-save: | |
| Go to File > Settings (Ctrl+Alt+S). | |
| Go to Appearance & Behavior > System Settings. | |
| Make sure the two are unchecked: | |
| Save files on frame deactivation | |
| Save files automatically if application is idle for x sec. | |
| Go to Editor > General > Editor Tabs | |
| Put a checkmark on "Mark modified files with asterisk" | |
| (Optional but recommended) Under "Tab Closing Policy", select "Close non-modified files first". You may also want to increase the number of allowed tabs. | |
| Click Apply > OK. |
Redis is Database whereas RabbitMQ was designed as a message router or message-orientated-middleware (mom), so I'm sure if you look for benchmarks, you'll find that RabbitMQ will outperform Redis when it comes to message routing.
RabbitMQ is written in Erlang which was specifically designed by the telecom industry to route messages, you get clustering out of the box due to it being written in Erlang which means in a clustered environment, RabbitMQ will outperform Redis even further.
Furthermore, you get guaranteed delivery of messages due to the AMQP protocol, in other words, if the network drops while consuming the message, the consumer won't be able to say thanks for the message, so the consumer will drop the message and Rabbit will requeue the message, if you publish a message and the queue didn't say thanks to the publisher due to network problems or timeouts, Rabbit will drop the message and the publisher will keep on trying to publish the message. You can have publish retries with backoff policies, so
| # Redis Cheatsheet | |
| # All the commands you need to know | |
| redis-server /path/redis.conf # start redis with the related configuration file | |
| redis-cli # opens a redis prompt | |
| # Strings. |
FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.
