| description | tools | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
Automated TDD workflow: write failing test, implement feature, verify passing test |
|
You are a Test-Driven Development automation expert. Your role is to execute the complete TDD cycle autonomously: Red → Green → Refactor.
🚨 NEVER write production code before writing a failing test.
| #user nobody; | |
| worker_processes 4; | |
| #error_log logs/error.log; | |
| #error_log logs/error.log notice; | |
| #error_log logs/error.log info; | |
| #pid logs/nginx.pid; |
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.
| #!/bin/bash | |
| # options: | |
| # remove stopped containers and untagged images | |
| # $ dkcleanup | |
| # remove all stopped|running containers and untagged images | |
| # $ dkcleanup --reset | |
| # remove containers|images|tags matching {repository|image|repository\image|tag|image:tag} | |
| # pattern and untagged images | |
| # $ dkcleanup --purge {image} |
For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.
Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon with HyperThreading enabled, but it can work without problem on slower machines.
You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.
| ####################################################################################################################### | |
| # This Gist is some crib notes/tests/practice/whatever for talking to Active Directory via LDAP. The (surprisingly | |
| # helpful) documentation for Net::LDAP can be found here: http://net-ldap.rubyforge.org/Net/LDAP.html | |
| ####################################################################################################################### | |
| require 'rubygems' | |
| require 'net/ldap' | |
| ####################################################################################################################### | |
| # HELPER/UTILITY METHOD |
Attention: the list was moved to
https://github.com/dypsilon/frontend-dev-bookmarks
This page is not maintained anymore, please update your bookmarks.
The reason why you might get certificate errors in Ruby 2.0 when talking HTTPS is because there isn't a default certificate bundle that OpenSSL (which was used when building Ruby) trusts.
Update: this problem is solved in edge versions of rbenv and RVM.
$ ruby -rnet/https -e "Net::HTTP.get URI('https://github.com')"
net/http.rb:917:in `connect': SSL_connect returned=1 errno=0 state=SSLv3
read server certificate B: certificate verify failed (OpenSSL::SSL::SSLError)
You can work around the issue by installing a certificate bundle that you trust. I trust Mozilla and curl.
