eko

Architecture as Code with the C4 model — a complete archyl.yaml example

A minimal but complete example of defining a software architecture as version-controlled YAML using the C4 model (System → Container → Component → Code).

Why Architecture as Code?

Diagrams drawn in GUI tools drift out of date the moment code changes. Keeping your C4 model in a plain-text file next to your code means it is:

• Version-controlled — history, blame, and rollbacks like any other file.
• Reviewed in pull requests — architecture changes are discussed where code is.

eko

eko

eko

eko

eko

Keybase proof

I hereby claim:

• I am eko on github.
• I am eko (https://keybase.io/eko) on keybase.
• I have a public key ASDkx5UjBTNnQ4i4yKaaKX1x0rurikh9fD0-xAdeMk_m7go

To claim this, I am signing this object:

eko

package main

import (
	"flag"
	"fmt"
	"github.com/rwcarlsen/goexif/exif"
	"os"
	"path"
	"path/filepath"
	"strings"

eko

package main

import (
    "encoding/json"
    "io/ioutil"
    "net/http"
    "fmt"
)

type RatpLine struct {

eko

tell application "Messages"
	set targetService to id of 1st service whose service type = iMessage
	
	set peopleICareAbout to {"Vincent Composieux"}
	set peopleAlreadySent to {}
	
	repeat with myBuddy in buddies
		set buddyFullname to full name of myBuddy
		set buddyFirstname to first name of myBuddy
		

eko

#!/usr/bin/python
#
# This script will provides a reverse-search on Packagist to find which libraries uses a given library package
# as a dependency.
#
# Usage:
# First, you need to fetch dependencies: ./packagist.py --fetch
# After, you can start checking packages: ./packagist.py --package <package-name>
#
# Author: Vincent Composieux <vincent.composieux@gmail.com>