miguelmota

package ciphers

import (
	"crypto/rand"
	"crypto/rsa"
	"crypto/sha512"
	"crypto/x509"
	"encoding/pem"
        "log"
)

chpio

import React from 'react';
import {Route, Link as RouterLink, withRouter} from 'react-router-dom';

function Link({to, location, children, staticContext, match, history, ...rest}) {
	/* eslint-disable react/jsx-no-bind */
	return (
		<Route
			render={() =>
				<RouterLink
					replace={to === location.pathname}

npearce

UPDATE (March 2020, thanks @ic): I don't know the exact AMI version but yum install docker now works on the latest Amazon Linux 2. The instructions below may still be relevant depending on the vintage AMI you are using.

Amazon changed the install in Linux 2. One no-longer using 'yum' See: https://aws.amazon.com/amazon-linux-2/release-notes/

Docker CE Install

sudo amazon-linux-extras install docker
sudo service docker start

dreampuf

Source: https://gitlab.com/gitlab-org/gitlab-runner/issues/1583#note_93170156

OK, I've experimented a lot getting this going with the docker+machine executor (specifically with the amazonec2 driver, which I suspect is quite common for people looking at this thread!), it may also be helpful to others when debugging what's going on for them.

docker+machine is interesting because it has several relevant contexts (i.e. a file system and environment variables), which I shall refer to as:

• "runner": what is running the gitlab-runner binary - in my case this is an ECS-managed docker container for the gitlab/gitlab-runner image on docker hub, but it could the systemd service configuration if you're running directly on the machine.
• "job host": the docker-machine created machine (e.g. EC2 instance) that runs the docker daemon
• "job container": the docker container for the image specified in the project .gitlab-ci.yaml (or the default in config.toml)

dsmrt

# this script queries aws logs with insights filtering on ERROR

# explanation of start and end times
#--start-time = unix timestamp 30 mins in the past
#--end-time = unix timestamp now

QUERY_ID=$(aws logs start-query \
 --profile $profile \
 --log-group-name /aws/lambda/aap-event-consumer-dev \
 --start-time `date -v-30M "+%s"` \

fridgerator

Lets Encrypt has removed their ACME V1 api in favor of ACME V2. The Rancher 1.6 catalog entry for Lets Encrypt certificates doesn't support this api. There is a forked version of the repo, however the service has to be created manually instead of from the catalog.

1. Create a new service, give it a name, use vxcontrol/rancher-letsencrypt:v1.0.0 for the image
2. In the "Volumes" tab, add a volume /var/lib/rancher:/var/lib/rancher
3. In the "Command" tab, set the "Console" option to none
4. Click to add an Environment Variable, and paste the following into the first "Variable" input field.

• All of the environment variables should auto-fill.
• Fill in the necessary values

wardbekker

<source>
  @type tail
  format none
  path /var/log/*.log
  pos_file positions.pos
  tag varlog.*
  path_key filename
</source>

<match varlog.**>

sebsto

# YouTube (english) : https://www.youtube.com/watch?v=FtU2_bBfSgM
# YouTube (french) : https://www.youtube.com/watch?v=VjnaVBnERDU

#
# On your laptop, connect to the Mac instance with SSH (similar to Linux instances)
#
ssh -i <your private key.pem> ec2-user@<your public ip address>

#
# On the Mac