Install

Install script

Install from source

Hello World

Shape

Basics

Example

Connections

Basics

Connection labels

Connections must reference a shape's key, not its label.

Example

Repeated connections

Connection chaining

Cycles are okay

Arrowheads

Containers

Nested syntax

Container labels

1. Shorthand container labels

2. Reserved keyword label

Example

Reference parent

The recommended way to install is to run our install script, which will figure out the best way to install based on your machine. E.g. if D2 is available through a package manager installed, it will use that package manager.

권장하는 설치 방법은 우리의 설치 스크립트를 실행하는 것입니다. 이 스크립트는 당신의 컴퓨터에 따라 가장 적합한 설치 방법을 찾아줍니다. 예를 들어, D2가 패키지 매니저를 통해 설치 가능한 경우에는 해당 패키지 매니저를 사용합니다.

# With --dry-run the install script will print the commands it will use
# to install without actually installing so you know what it's going to do.
curl -fsSL https://d2lang.com/install.sh | sh -s -- --dry-run
# If things look good, install for real.
curl -fsSL https://d2lang.com/install.sh | sh -s --

Follow the instructions, if any. Test your installation was successful by running d2 version.

If you want to uninstall:

curl -fsSL https://d2lang.com/install.sh | sh -s -- --uninstall

Alternatively, you can install from source:

대신 소스에서 설치할 수 있습니다:

go install oss.terrastruct.com/d2

x -> y: hello world

You can declare shapes like so:

imAShape
im_a_shape
im a shape
i'm a shape
# notice that one-hyphen is not a connection
# whereas, `a--shape` would be a connection
a-shape

You can also use semicolons to define multiple shapes on the same line:

하나의 줄에 여러 개의 도형을 정의하려면 세미콜론을 사용할 수 있습니다:

1SQLite; Cassandra

By default, a shape's label is the same as the shape's key. But if you want it to be different, assign a new label like so:

기본적으로 도형의 라벨은 도형의 키와 같습니다. 하지만 다른 라벨을 원한다면 다음과 같이 새 라벨을 할당하세요:

1pg: PostgreSQL

By default, a shape's type is rectangle. To specify otherwise, provide the field shape:

기본적으로 도형의 유형은 사각형입니다. 다른 유형을 지정하려면 shape 필드를 제공하십시오:

Cloud: my cloud
Cloud.shape: cloud

pg: PostgreSQL
Cloud: my cloud
Cloud.shape: cloud
SQLite; Cassandra

Connections define relationships between shapes.

연결은 도형 간의 관계를 정의합니다.

Hyphens/arrows in between shapes define a connection.

도형 사이의 하이픈/화살표는 연결을 정의합니다.

Write Replica Canada <-> Write Replica Australia

Read Replica <- Master
Write Replica -> Master

Read Replica 1 -- Read Replica 2

If you reference an undeclared shape in a connection, it's created (as shown in the hello world example).

연결에서 선언되지 않은 도형을 참조하면, hello world 예제에서 보여지듯이, 도형이 생성됩니다.

Read Replica 1 -- Read Replica 2: Kept in sync

연결은 모양의 라벨이 아닌 키를 참조해야합니다.

be: Backend
fe: Frontend

# This would create new shapes
Backend -> Frontend

# This would define a connection over existing labels
be -> fe

Write Replica Canada <-> Write Replica Australia

Read Replica <- Master

x -- y

super long shape id here --\
  -> super long shape id even longer here

Repeated connections do not override existing connections. They declare new ones.

반복 연결은 기존 연결을 덮어쓰지 않습니다. 새로운 연결을 선언합니다.

Database -> S3: backup
Database -> S3
Database -> S3: backup

For readability, it may look more natural to define multiple connection in a single line.

가독성을 위해 여러 연결을 한 줄에 정의하는 것이 더 자연스러울 수 있습니다.

# The label applies to each connection in the chain.
High Mem Instance -> EC2 <- High CPU Instance: Hosted By

Stage One -> Stage Two -> Stage Three -> Stage Four
Stage Four -> Stage One: repeat

To override the default arrowhead shape or give a label next to arrowheads, define a special shape on connections named source-arrowhead and/or target-arrowhead.

기본 화살표 머리 모양을 덮어쓰거나 화살표 머리 옆에 레이블을 지정하려면, 연결에 대한 특수한 모양을 source-arrowhead 및/또는 target-arrowhead로 정의하십시오.

a: The best way to avoid responsibility is to say, "I've got responsibilities"
b: Whether weary or unweary, O man, do not rest
c: I still maintain the point that designing a monolithic kernel in 1991 is a

a -> b: To err is human, to moo bovine {
  source-arrowhead: 1
  target-arrowhead: * {
    shape: diamond
  }
}

b <-> c: "Reality is just a crutch for people who can't handle science fiction" {
  source-arrowhead.label: 1
  target-arrowhead: * {
    shape: diamond
    style.filled: true
  }
}

d: A black cat crossing your path signifies that the animal is going somewhere

d -> a -> c

server
# Declares a shape inside of another shape
server.process

# Can declare the container and child in same line
im a parent.im a child

# Since connections can also declare keys, this works too
apartment.Bedroom.Bathroom -> office.Spare Room.Bathroom: Portal

You can avoid repeating containers by creating nested maps.

중첩된 맵을 만들어 반복적인 컨테이너를 피할 수 있습니다.

clouds: {
  aws: {
    load_balancer -> api
    api -> db
  }
  gcloud: {
    auth -> db
  }

  gcloud -> aws
}

There are two ways define container labels.

컨테이너 라벨을 정의하는 두 가지 방법이 있습니다.

gcloud: Google Cloud {
  ...
}

gcloud: {
  label: Google Cloud
  ...
}

clouds: {
  aws: AWS {
    load_balancer -> api
    api -> db
  }
  gcloud: Google Cloud {
    auth -> db
  }

  gcloud -> aws
}

users -> clouds.aws.load_balancer
users -> clouds.gcloud.auth

ci.deploys -> clouds

Sometimes you want to reference something outside of the container from within. The underscore (_) refers to parent.

가끔은 컨테이너 외부의 것을 참조하고 싶을 때가 있습니다. 밑줄(_)은 부모를 참조합니다.

christmas: {
  presents
}
birthdays: {
  presents
  _.christmas.presents -> presents: regift
  _.christmas.style.fill: "\#ACE1AF"
}