| ### Add those lines after *filter near the beginning of the file | |
| :ufw-http - [0:0] | |
| :ufw-http-logdrop - [0:0] | |
| ### Add those lines near the end of the file | |
| ### Start HTTP ### |
| # using such a setup requires `apt-get install lua-nginx-redis` under Ubuntu Trusty | |
| # more info @ http://wiki.nginx.org/HttpLuaModule#access_by_lua | |
| http { | |
| lua_package_path "/etc/nginx/include.d/?.lua;;"; | |
| lua_socket_pool_size 100; | |
| lua_socket_connect_timeout 10ms; | |
| lua_socket_read_timeout 10ms; | |
| server { |
Once in a while, you may need to cleanup resources (containers, volumes, images, networks) ...
// see: https://github.com/chadoe/docker-cleanup-volumes
$ docker volume rm $(docker volume ls -qf dangling=true)
$ docker volume ls -qf dangling=true | xargs -r docker volume rm
| #!/bin/bash | |
| HOSTS=(PUT, YOUR, HOSTS, HERE) | |
| CMD="tail -f logs/api.log" | |
| echo "Hit CTRL-C to stop" | |
| sleep 0.5 | |
| PIDS="" | |
| for host in ${HOSTS[*]} | |
| do |
In progress thoughts about introducing Conduit into our clusters.
All our Kubernetes manifests are defined in Git and applied to the cluster via automated deployment pipelines. The standard procedure to deploy is to introduce a change to this git repo (these changes are themselves automated), which is then applied to the k8s cluster.
Conduit is a departure from this because it encourages an injection process which relies on an out of repo dependency (other than kubernetes itself). The objects that end up in Kubernetes are NOT defined in Git, and are a function of our own manifests plus the version of Conduit that happens to be installed locally (in the CD environment). This makes people nervous.