| function getLambdaEventSource(event) { | |
| if (event.Records && event.Records[0].cf) return 'isCloudfront'; | |
| if (event.configRuleId && event.configRuleName && event.configRuleArn) return 'isAwsConfig'; | |
| if (event.Records && (event.Records[0].eventSource === 'aws:codecommit')) return 'isCodeCommit'; | |
| if (event.authorizationToken === "incoming-client-token") return 'isApiGatewayAuthorizer'; | |
| if (event.StackId && event.RequestType && event.ResourceType) return 'isCloudFormation'; |
When hosting our web applications, we often have one public IP
address (i.e., an IP address visible to the outside world)
using which we want to host multiple web apps. For example, one
may wants to host three different web apps respectively for
example1.com, example2.com, and example1.com/images on
the same machine using a single IP address.
How can we do that? Well, the good news is Internet browsers
If you use git on the command-line, you'll eventually find yourself wanting aliases for your most commonly-used commands. It's incredibly useful to be able to explore your repos with only a few keystrokes that eventually get hardcoded into muscle memory.
Some people don't add aliases because they don't want to have to adjust to not having them on a remote server. Personally, I find that having aliases doesn't mean I that forget the underlying commands, and aliases provide such a massive improvement to my workflow that it would be crazy not to have them.
The simplest way to add an alias for a specific git command is to use a standard bash alias.
# .bashrc