Skip to content

Instantly share code, notes, and snippets.

View mk4dir's full-sized avatar
🐧

Kadir Karakoc mk4dir

🐧
View GitHub Profile
www.google.com
alt.aspmx.1.google.com
client.1.google.com
clients.1.google.com
gmail-smtp-mas.1.google.com
misc-anycast.1.google.com
104-cache-blicnet.google.com
119-cache-blicnet.google.com
216-239-45-10.google.com
31.google.com
@Evalle
Evalle / gist:7b21e0357c137875a03480428a7d6bf6
Created October 20, 2017 12:08
How to configure Docker to use external DNS server
Either via
$ docker run --dns 10.0.0.2 busybox nslookup google.com
or edit your /etc/docker/daemon.json to have something like:
{
"dns": ["10.0.0.2", "8.8.8.8"]
}
then restart docker service

I have been an aggressive Kubernetes evangelist over the last few years. It has been the hammer with which I have approached almost all my deployments, and the one tool I have mentioned (shoved down clients throats) in almost all my foremost communications with clients, and it was my go to choice when I was mocking my first startup (saharacluster.com).

A few weeks ago Docker 1.13 was released and I was tasked with replicating a client's Kubernetes deployment on Swarm, more specifically testing running compose on Swarm.

And it was a dream!

All our apps were already dockerised and all I had to do was make a few modificatons to an existing compose file that I had used for testing before prior said deployment on Kubernetes.

And, with the ease with which I was able to expose our endpoints, manage volumes, handle networking, deploy and tear down the setup. I in all honesty see no reason to not use Swarm. No mission-critical feature, or incredibly convenient really nice to have feature in Kubernetes that I'm go

RacerX
10/26/2016
Thomas Stoeckert
11/30/2016
Thomas Stoeckert
1/26/2018
WSL pebble building
@milmazz
milmazz / imposter-handbook-links.md
Last active January 17, 2025 12:36
Useful links found in The Imposter's Handbook by Rob Conery
@brianlmoon
brianlmoon / apache_cors_example
Last active April 22, 2025 09:41
CORS example for Apache with multiple domains
# Sets CORS headers for request from example1.com and example2.com pages
# for both SSL and non-SSL
SetEnvIf Origin "^https?://[^/]*(example1|example2)\.com$" ORIGIN=$0
Header set Access-Control-Allow-Origin %{ORIGIN}e env=ORIGIN
Header set Access-Control-Allow-Credentials "true" env=ORIGIN
# Always set Vary: Origin when it's possible you may send CORS headers
Header merge Vary Origin