Josh Samuel jsamuel1

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

General rules

Follow standard conventions.
Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
Boy scout rule. Leave the campground cleaner than you found it.
Always find root cause. Always look for the root cause of a problem.

Design rules

Docker - How to cleanup (unused) resources

Cleanup resources (containers, volumes, images, networks) ...

delete volumes

// see: https://github.com/chadoe/docker-cleanup-volumes

$ docker volume rm $(docker volume ls -qf dangling=true)

$ docker volume ls -qf dangling=true | xargs -r docker volume rm

The repository for the assignment is public and Github does not allow the creation of private forks for public repositories.

The correct way of creating a private frok by duplicating the repo is documented here.

For this assignment the commands are:

Create a bare clone of the repository. (This is temporary and will be removed so just do it wherever.)

git clone --bare [email protected]:usi-systems/easytrace.git

	#!/bin/bash
	curl -s 'https://api.regional-table.region-services.aws.a2z.com/index.json' \
	\| jq '.prices[] \| .attributes \| .["aws:region"], .["aws:serviceName"]' \
	\| sed '$!N;s/\n/,/'

	# MIT No Attribution
	#
	# Copyright 2022 Ben Kehoe
	#
	# Permission is hereby granted, free of charge, to any person obtaining a copy of this
	# software and associated documentation files (the "Software"), to deal in the Software
	# without restriction, including without limitation the rights to use, copy, modify,
	# merge, publish, distribute, sublicense, and/or sell copies of the Software, and to
	# permit persons to whom the Software is furnished to do so.
	#

	git checkout -b upstream
	git remote add upstream [email protected]/upstream1/blah.git
	git fetch upstream # or use -f in git remote add
	git merge -s subtree upstream/master --allow-unrelated-histories -X theirs

	{
	"Version": "2012-10-17",
	"Statement": [
	{
	"Action": [
	"apigateway:*",
	"autoscaling:*",
	"cloudtrail:*",
	"cloudwatch:*",
	"cloudformation:*",

	AWS::AmazonMQ::Broker
	AWS::AmazonMQ::Configuration
	AWS::ApiGateway::Account
	AWS::ApiGateway::ApiKey
	AWS::ApiGateway::Authorizer
	AWS::ApiGateway::BasePathMapping
	AWS::ApiGateway::ClientCertificate
	AWS::ApiGateway::Deployment
	AWS::ApiGateway::DocumentationPart
	AWS::ApiGateway::DocumentationVersion

	@ECHO off
	:top
	CLS
	ECHO Choose a shell:
	ECHO [1] cmd
	ECHO [2] bash
	ECHO [3] PowerShell
	ECHO [4] PowerShell Core
	ECHO [5] Python
	ECHO.


	#!/bin/bash
	#set -x

	# Shows you the largest objects in your repo's pack file.
	# Written for osx.
	#
	# @see http://stubbisms.wordpress.com/2009/07/10/git-script-to-show-largest-pack-objects-and-trim-your-waist-line/
	# @author Antony Stubbs