Skip to content

Instantly share code, notes, and snippets.

@afarid
afarid / php profiling
Created June 29, 2020 19:13
php profiling
# Profiling single php request
The goal of this document is to give instructions for enable profiling
Steps:
## Enable php xdebug module
```bash
PHP_VERSION=7.2
cat > /etc/php/7.2/apache2/conf.d/20-xdebug.ini <<EOF
zend_extension=xdebug.so
xdebug.profiler_enable_trigger=1
@r0mdau
r0mdau / find-k8snode-interface.sh
Last active November 9, 2024 21:16
How to get tcpdump for containers inside Kubernetes pods
# find the kube node of the running pod, appear next to hostIP, and note containerID hash
kubectl get pod mypod -o json
# -> save hostIP
# -> save containerID
# connect to the node and find the pods unique network interface index inside it's container
docker exec containerID /bin/bash -c 'cat /sys/class/net/eth0/iflink'
# -> returns index
# locate the interface of the node
@bobrik
bobrik / README.md
Last active March 27, 2025 02:16
CFS hiccups
@so0k
so0k / kubectl.md
Last active February 19, 2026 16:57
Playing with kubectl output

Kubectl output options

Let's look at some basic kubectl output options.

Our intention is to list nodes (with their AWS InstanceId) and Pods (sorted by node).

We can start with:

kubectl get no
@wojteklu
wojteklu / clean_code.md
Last active March 21, 2026 11:21
Summary of 'Clean code' by Robert C. Martin

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.


General rules

  1. Follow standard conventions.
  2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
  3. Boy scout rule. Leave the campground cleaner than you found it.
  4. Always find root cause. Always look for the root cause of a problem.

Design rules

@JonCole
JonCole / Redis-BestPractices-General.md
Last active December 2, 2025 10:45
Redis Best Practices

Some of the Redis best practices content has moved

This content from this markdown file has moved a new, happier home where it can serve more people. Please check it out : https://docs.microsoft.com/azure/azure-cache-for-redis/cache-best-practices.

NOTE: Client specific guidance listed below is still valid and should still be considered. I will update this document once all content has been moved.

@thomasst
thomasst / migrate-redis.py
Created May 14, 2015 18:26
Migrate Redis data on Amazon ElastiCache
"""
Copies all keys from the source Redis host to the destination Redis host.
Useful to migrate Redis instances where commands like SLAVEOF and MIGRATE are
restricted (e.g. on Amazon ElastiCache).
The script scans through the keyspace of the given database number and uses
a pipeline of DUMP and RESTORE commands to migrate the keys.
Requires Redis 2.8.0 or higher.