In Git you can add a submodule to a repository. This is basically a repository embedded in your main repository. This can be very useful. A couple of usecases of submodules:
- Separate big codebases into multiple repositories.
// Based on https://github.com/jaubourg/ajaxHooks/blob/master/src/ajax/xdr.js | |
(function( jQuery ) { | |
if ( window.XDomainRequest && !jQuery.support.cors ) { | |
jQuery.ajaxTransport(function( s ) { | |
if ( s.crossDomain && s.async ) { | |
if ( s.timeout ) { | |
s.xdrTimeout = s.timeout; | |
delete s.timeout; |
Magic words:
psql -U postgres
Some 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)<# | |
NOTE: DO NOT RUN THIS SCRIPT | |
This is simply a record of commands | |
demonstrated in the AWS PowerShell Webinar | |
#> | |
#Credentials | |
Get-EC2Instance -AccessKey $AccessKey -SecretKey $SecretKey -Region us-west-1 |
No, you are not allowed to change the copyright notice. Indeed, the license text states pretty clearly:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
But you are allowed to add a copyright notice.
If you want to keep the MIT license, which is what I would advise you to do, you only need to add a single line to the license file, before or after Copyright (c) 2012 Some Name
with your own copyright notice. The final LICENSE
file will look like this:
The MIT License (MIT)
Mute these words in your settings here: https://twitter.com/settings/muted_keywords | |
ActivityTweet | |
generic_activity_highlights | |
generic_activity_momentsbreaking | |
RankedOrganicTweet | |
suggest_activity | |
suggest_activity_feed | |
suggest_activity_highlights | |
suggest_activity_tweet |
ARG atlantis_version=v0.15.0 | |
FROM runatlantis/atlantis:${atlantis_version} | |
LABEL maintainer="Beat DevOps Team" | |
LABEL description="thebeat.co atlantis image used in IaC CI/CD!" | |
LABEL version="0.2" | |
# https://github.com/gruntwork-io/terragrunt/releases | |
ARG terragrunt_version=v0.25.1 |
One of biggest barriers when trying to get started with Kubernetes is that there's so much content out there that it's kinda overwhelming - and that's totally normal! The intent of this document is to try and provide directed resources in a roadmap like fashion to understand and learn about the horizontals of Kubernetes - post which you can dive deep into any vertical while keeping the bigger picture in mind - that this document hopes to provide.
This is a set of resources for different topics that I found particularly helpful when getting started, and hopefully you do too! I've tried to list them out in order of consumption. If A comes before B under a subtopic, then it's probably that A has topics needed for B, or that A attempts to explain topics of B in a slightly simpler (not nescessarily better) manner than B.
Feel free to skip over if you're already familiar with containers and have some idea about what they are and why they exist.