Source:http://stackoverflow.com/questions/224664/difference-between-proxy-server-and-reverse-proxy-server
First of all, the word "proxy" describes someone or something acting on behalf of someone else. In the computer realm, we are talking about one server acting on the behalf of another computer. For the purposes of accessibility, I will limit my discussion to web proxies - however, the idea of a proxy is not limited to web sites.
DynamoDB is a powerful, fully managed, low latency, NoSQL database service provided by Amazon. DynamoDB allows you to pay for dedicated throughput, with predictable performance for "any level of request traffic". Scalability is handled for you, and data is replicated across multiple availability zones automatically. Amazon handles all of the pain points associated with managing a distributed datastore for you, including replication, load balancing, provisioning, and backups. All that is left is for you to take your data, and its access patterns, and make it work in the denormalized world of NoSQL.
The single most important part of using DynamoDB begins before you ever put data into it: designing the table(s) and keys. Keys (Amazon calls them primary keys) can be composed of one attribute, called a hash key, or a compound key called the hash and range key. The key is used to uniquely identify an item in a table. The choice of the primary key is particularl
Magic words:
psql -U postgresSome interesting flags (to see all, use -h or --help depending on your psql version):
-E: will describe the underlaying queries of the \ commands (cool for learning!)-l: psql will list all databases and then exit (useful if the user you connect with doesn't has a default database, like at AWS RDS)
| 8.2.3. HTTP log format | |
| ---------------------- | |
| The HTTP format is the most complete and the best suited for HTTP proxies. It | |
| is enabled by when "option httplog" is specified in the frontend. It provides | |
| the same level of information as the TCP format with additional features which | |
| are specific to the HTTP protocol. Just like the TCP format, the log is usually | |
| emitted at the end of the session, unless "option logasap" is specified, which | |
| generally only makes sense for download sites. A session which matches the | |
| "monitor" rules will never logged. It is also possible not to log sessions for |
I feel your pain. SSL is tough and is probably the number one stumbling block for new users getting Puppet working in their environment. Hopefully this answer helps reduce frustration and get you up and running. The good news is, once it's set up right, you won't have to fiddle with it any more.
First, make sure the problem you're having is actually an SSL problem. Almost all of the SSL-related error messages on the client start with the string SSL_connect and then the error raised up by the underlying crypto libraries. General networking errors will not have this string, so normal network troubleshooting methodology applies; specifically, Connection refused - connect(2) means a TCP connection attempt got a RST packet indicating a firewall or puppet master not running, and getaddrinfo: nodename nor servname provided, or not known means the server's hostname (the value of puppet agent --configprint server) was not resolvable in DNS/hosts.
Next, assuming you do have an SSL_connect style error, it
| // Channels-driven concurrency with Go | |
| // Code examples from Rob Pike's talk on Google I/O 2012: | |
| // http://www.youtube.com/watch?v=f6kdp27TYZs&feature=youtu.be | |
| // | |
| // Concurrency is the key to designing high performance network services. | |
| // Go's concurrency primitives (goroutines and channels) provide a simple and efficient means | |
| // of expressing concurrent execution. In this talk we see how tricky concurrency | |
| // problems can be solved gracefully with simple Go code. | |
| // (1) Generator: function that returns the channel |
| This playbook has been removed as it is now very outdated. |
| #!/usr/bin/env ruby | |
| # This pre-commit hook will prevent any commit to forbidden branches | |
| # (by default, "staging" and "production"). | |
| # Put this file in your local repo, in the .git/hooks folder | |
| # and make sure it is executable. | |
| # The name of the file *must* be "pre-commit" for Git to pick it up. | |
| FORBIDDEN_BRANCHES = ["staging", "production"] |
| # How to sign your custom RPM package with GPG key | |
| # Step: 1 | |
| # Generate gpg key pair (public key and private key) | |
| # | |
| # You will be prompted with a series of questions about encryption. | |
| # Simply select the default values presented. You will also be asked | |
| # to create a Real Name, Email Address and Comment (comment optional). | |
| # | |
| # If you get the following response: |
| INSTALL | |
| ======= | |
| $ gem install rspec | |
| RSPEC-RAILS | |
| =========== | |
| RAILS-3 | |
| ======= |