Steven Jack stevenjack

## config
[default]
aws_access_key_id=blah
aws_secret_access_key=blah
region=eu-west-1

## test.php
<?php

class Test
{
    protected $item = array('test');

    public function output()
    {
        echo "Item without {}: $this->item[0]\n";
        echo "item with {}: {$item[0]}";

## Guardfile
require 'terminal-notifier-guard'

# Simple guard file for running go tests
guard :shell do
  watch(/(.*).go/) do |m|
    `go test`.tap do |output|
      if $? == 0
        TerminalNotifier::Guard.success("\u2705 All tests passed")
      else
        TerminalNotifier::Guard.failed("\u26D4 Some tests failed")

## policy.json
{
  "Version": "2008-10-17",
  "Id": "AlarmTopicPolicy",
  "Statement": [
    {
      "Sid": "Allow-Publish-Subscribe-AlarmTopicPolicy",
      "Effect": "Allow",
      "Principal": {
        "AWS": "*"
      },

## 0_reuse_code.js
// Use Gists to store code you would like to remember later on
console.log(window); // log the "window" object to the console

## watch_tower.go
package main

import (
	"fmt"
	"net/http"
	"sync"
	"time"
)

func main() {

## foo.txyt
0xecc6b20d3ccac1ee9ef109af5a7cdb85706b1df9

## 29_04_2018_contributions.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                stevenjack
                / 29_04_2018_contributions.md
            
            
              Created
              April 30, 2018 18:37
            
          
    Contributions 29/04/2018


Added simple docker-compose support for running a cluster of 4 neo-go nodes to start working on consensus and eventually form part of the integration tests - nspcc-dev/neo-go#74.
Looked into issue which seemed to be the user having an issue with neo-python not neo-go 😂 - nspcc-dev/neo-go#75.


## background_service.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                stevenjack
                / background_service.md
            
            
              Created
              May 16, 2018 14:01
            
          
    Create a new background service


Copy the stack folder from aws-stacks/{stack_name} to compute/ecs/services/{stack_name}.
Update provider sections to be inline with other services in that repo (Add version to providers and key to s3 backend config).
Add modules/ecs/service/background module and supporting terraform data to be used in the module.
Run t plan in assume-role container.
Note down path for any resources that already exist (KMS, dynamoDB, SQS etc).
Look up resource in terraform docs and find out syntax for import, KMS example: t import path.to.kms.key.resource arn::for::kms::key.
Create resource with t apply -auto-approve.
Go to repo of service, and the following to the Dockerfile:
	[default]
	aws_access_key_id=blah
	aws_secret_access_key=blah
	region=eu-west-1
	<?php

	class Test
	{
	protected $item = array('test');

	public function output()
	{
	echo "Item without {}: $this->item[0]\n";
	echo "item with {}: {$item[0]}";
	require 'terminal-notifier-guard'

	# Simple guard file for running go tests
	guard :shell do
	watch(/(.*).go/) do \|m\|
	`go test`.tap do \|output\|
	if $? == 0
	TerminalNotifier::Guard.success("\u2705 All tests passed")
	else
	TerminalNotifier::Guard.failed("\u26D4 Some tests failed")
	{
	"Version": "2008-10-17",
	"Id": "AlarmTopicPolicy",
	"Statement": [
	{
	"Sid": "Allow-Publish-Subscribe-AlarmTopicPolicy",
	"Effect": "Allow",
	"Principal": {
	"AWS": "*"
	},
	// Use Gists to store code you would like to remember later on
	console.log(window); // log the "window" object to the console
	package main

	import (
	"fmt"
	"net/http"
	"sync"
	"time"
	)

	func main() {