lakshmantgld

A Webhook, in simple terms, is a user-defined HTTP callback. It is a mechanism for the system to notify you about an event. In our case, we need to send messages to a particular channel in slack. Slack calls in Incoming Webhook. It is a mechanism to send messages to your Slack Channel from external sources. These external sources could be any application or service that is capable of sending a JSON payload over HTTP into a Slack Channel. Each Channel will be identified by a unique Incoming Webhook URL to which you can post the message from outside. This configuration is done via the Integrations for your channel.

Steps to create a incoming webhook in Slack:

1. Naviagte to the Incoming Webhook URL. Click the hyper link incoming webhook integration below the heading Incoming Webhooks.
2. You will be asked to enter your team URL, followed by your slack credentials.
3. Once you have completed the above step, you will see the wizard kind of webpage to

joshRpowell

•100% [I] ➜ rvm get master && rvm list known
Downloading https://get.rvm.io
Downloading https://raw.githubusercontent.com/rvm/rvm/master/binscripts/rvm-installer.asc
Verifying /Users/jpowell/.rvm/archives/rvm-installer.asc
gpg: Signature made Sat Sep  9 15:49:18 2017 EDT
gpg:                using RSA key E206C29FBF04FF17
gpg: Good signature from "Michal Papis (RVM signing) <[email protected]>" [unknown]
gpg: Note: This key has expired!
Primary key fingerprint: 409B 6B17 96C2 7546 2A17  0311 3804 BB82 D39D C0E3
     Subkey fingerprint: 62C9 E5F4 DA30 0D94 AC36  166B E206 C29F BF04 FF17

jlis

image: docker:latest

variables:
  REPOSITORY_URL: <AWS ACCOUNT ID>.dkr.ecr.eu-central-1.amazonaws.com/<ECS REPOSITORY NAME>
  REGION: eu-central-1
  TASK_DEFINTION_NAME: <TASK DEFINITION NAME>
  CLUSTER_NAME: <CLUSTER NAME>
  SERVICE_NAME: <SERVICE NAME>

services:

casprine

$base: 15;

@function em($pixels, $context: $base) {
    @if (unitless($pixels)) {
        $pixels: $pixels * 1px;
    }

    @if (unitless($context)) {
        $context: $context * 1px;
    }

giuliocalzolari

---
###Cloudwatch role should be attached to the ec2 instance###
- hosts: dd    ###servers on which you need to run the cw_agent
  become: yes
  remote_user: root
  gather_facts: true
  tasks:
    - name: Check if Cloudwatch Agent is Installed Already
      shell: /opt/aws/amazon-cloudwatch-agent/bin/amazon-cloudwatch-agent-ctl -m ec2 -a status
      register: init_status_result

OliverMensahDev

Journey into writing code that is readable, understandable ,maintainable and testable as well as how to prepare codebase to embrace future changes.

I wonder from time to time whether I'm doing the right thing with respect to guidelines and principles when using an object-oriented programming approach to create application. I started reading Object Design Style Guide book last year to learn more about objects. And beginning this year, I decided to delve deeper into writing code that is readable, understandable and maintainable as well as how to prepare codebase to embrace future changes.

Here are the resources used:

Book

• Object Design Style Guide:
• Principles of Package Design

Pluralsight Courses

• Writing Readable and Maintainable Code

jpate24

#for machine in $(aws ec2 describe-regions --output text | awk {'print $4'})
#do
#    echo $machine
#done


for volume in $(aws ec2 describe-volumes --region us-east-1 --output text | grep available | awk '{print $8}' | grep vol | tr '\n' ' ')
do
    echo "deleting $volume"
    aws ec2 delete-volume --volume-id $volume

mherrmann

As of May 29, 2021, the available Linode types are:

g6-nanode-1
g6-standard-1
g6-standard-2
g6-standard-4
g6-standard-6
g6-standard-8
g6-standard-16
g6-standard-20

GordonOus

========== First =========
Lets compare both keys provided:

openssl rsa -pubin -inform PEM -text -noout < key1.pem
openssl rsa -pubin -inform PEM -text -noout < key2.pem

we can observe that both keys have SIMILAR modulus but DIFFERENT exponents: 
after googling online on RSA attacks i found one for Common Modulus

Exploiting it according to me was not very trivial especially without solid background in crypto (google to the rescue)

Carlos-Augusto

#The following commands helps cleaning a git repo when there are many pr that are done.
git pull  --all
for gone in $(git branch -vv | grep ': gone]' | awk '{print $1}'); do git branch -D $gone; done