You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+45-14Lines changed: 45 additions & 14 deletions
Original file line number
Diff line number
Diff line change
@@ -20,34 +20,57 @@
20
20
<a href="https://azimutt.app/slack" target="_blank"><img src="assets/slack-join.svg" alt="Join us on Slack" style="width: 216px; height: 54px;" width="216" height="54"></a>
21
21
</p>
22
22
23
-
Azimutt is a full-stack database exploration tool, from modern ERD made for real world databases (big & messy), to fast data navigation, but also documentation everywhere and whole database analysis.
23
+
Azimutt is a **full-stack database exploration tool**.
24
+
From modern ERD made for real world databases (big & messy), to fast data navigation, but also documentation everywhere and whole database analysis.
Databases existed for more than 40 years and despite a lot of tool around them, we couldn't find any providing a great exploration experience.
30
31
31
-
-**Database clients**focus on querying experience, with auto-completion and table/column lists but no visual help
32
-
-**ERDs**have a great diagram UI but fall short when schema is growing (real-world use cases)
33
-
-**Data catalogs**are focused on data governance and lineage for data teams, miss relational db for developers
32
+
-**ERDs**have a great diagram UI, but fall short when schema is growing (real-world use cases)
33
+
-**Data catalogs**are focused on data governance and lineage, missing relational db knowledge
34
+
-**Database clients**focus on querying with auto-completion and table/column lists, but no visual help
34
35
35
-
So we decided to built it 💪
36
+
So we decided to build the missing tool 💪
36
37
37
-
Azimutt started as a schema exploration tool for databases with hundreds of tables, but now it has grown a lot:
38
+
We started with schema exploration for databases with hundreds of tables, but now, it has grown a lot:
38
39
39
-
- Design your schema using [AML](https://azimutt.app/aml) for a fast diagramming
40
-
- Explore your database schema using search everywhere, display only useful tables/columns and follow relations
41
-
- Query your data like never before, follow foreign keys and display entities in diagram
42
-
- Document using table/column notes and tags and layouts and memos for use cases, features or team scopes
43
-
- Analyze it to discover inconsistencies and best practices to apply
40
+
-**Design** your schema using [AML](https://azimutt.app/aml) for a fast diagramming
41
+
-**Explore** your schema using search everywhere, display only useful tables/columns and follow relations
42
+
-**Query** your data like never before, follow foreign keys and display entities in diagram
43
+
-**Document** using table/column notes and tags, layouts and memos for use cases, features or team scopes
44
+
-**Analyze** it to discover inconsistencies and best practices to apply
44
45
45
-
Azimutt goal is to be your ultimate tool to understand your database.
46
+
Azimutt goal is to be your **ultimate tool to understand your database**.
46
47
47
-
## Self hosted
48
+
49
+
## Azimutt badge
50
+
51
+
You can load any public SQL file in Azimutt with just an url parameter.
52
+
So if you have a SQL file in your repo, like [structure.sql](./backend/priv/repo/structure.sql), you can add a button allowing your visitors to quickly explore it:
53
+
54
+
```markdown
55
+
[](https://azimutt.app/create?sql=https://raw.githubusercontent.com/azimuttapp/azimutt/refs/heads/main/backend/priv/repo/structure.sql)
56
+
```
57
+
58
+
Here are some examples:
59
+
60
+
[](https://azimutt.app/create?sql=https://raw.githubusercontent.com/azimuttapp/azimutt/refs/heads/main/backend/priv/repo/structure.sql)
61
+
[](https://azimutt.app/create?sql=https://raw.githubusercontent.com/azimuttapp/azimutt/refs/heads/main/backend/priv/repo/structure.sql)
62
+
[](https://azimutt.app/create?sql=https://raw.githubusercontent.com/azimuttapp/azimutt/refs/heads/main/backend/priv/repo/structure.sql)
63
+
64
+
Or use our custom button image:
65
+
66
+
[](https://azimutt.app/create?sql=https://raw.githubusercontent.com/azimuttapp/azimutt/refs/heads/main/backend/priv/repo/structure.sql)
67
+
68
+
69
+
## Self-hosted
48
70
49
71
You can use our [Docker image](https://github.com/azimuttapp/azimutt/pkgs/container/azimutt) to easily deploy it. Here is the [full guide](INSTALL.md).
50
72
73
+
51
74
## Deploy on Heroku
52
75
53
76
You can use our Heroku template which includes Azimutt web app, a Postgres database, Stackhero S3 storage and Mailgun.
Finally you will need to create the `azimutt` bucket on Stackhero:
96
+
Finally, you will need to create the `azimutt` bucket on Stackhero:
74
97
75
98
- connect to Stackhero from your Heroku dashboard
76
99
- use values of `S3_ROOT_ACCESS_KEY` and `S3_ROOT_SECRET_KEY` to log in
77
100
- create a bucket named `azimutt`
78
101
102
+
79
103
## Deploy on Kubernetes
80
104
81
105
Please read this [guide](./charts/azimutt/README.md)
82
106
107
+
83
108
## Local development
84
109
85
110
Azimutt is built with [Elixir](https://elixir-lang.org)/[Phoenix](https://www.phoenixframework.org) (backend & admin) and [Elm](https://elm-lang.org)/[elm-spa](https://www.elm-spa.dev) (editor).
@@ -101,6 +126,7 @@ Other things:
101
126
- API documentation is accessible at [`/api/v1/swagger`](http://localhost:4000/api/v1/swagger)
102
127
- You can use `pnpm --filter "azimutt-editor" run book` to start Elm design system & components, and access it with [localhost:4002](http://localhost:4002)
103
128
129
+
104
130
### command semantics
105
131
106
132
We have a lot of projects with a lot of commands, here is how they are structured:
@@ -116,10 +142,12 @@ We have a lot of projects with a lot of commands, here is how they are structure
116
142
-`build:docker` same as `build` but in the docker image (paths are different 😕)
117
143
-`update` bumps library versions
118
144
145
+
119
146
### Development commands
120
147
121
148
-`pnpm --filter "azimutt-editor" run book` to launch the Elm design system
122
149
150
+
123
151
### Setup Stripe
124
152
125
153
#### Config
@@ -129,6 +157,7 @@ We have a lot of projects with a lot of commands, here is how they are structure
129
157
- Copy your webhook signing secret to `STRIPE_WEBHOOK_SIGNING_SECRET` variable in your `.env` file (looks like `whsec_...`)
130
158
- Go to [your Stripe dashboard](https://dashboard.stripe.com/test/apikeys) to obtain your API Key and copy it into `STRIPE_API_KEY` in your `.env` file (looks like: `sk_test_...`)
131
159
160
+
132
161
#### Payments
133
162
134
163
When testing interactively, use a card number, such as `4242 4242 4242 4242`. Enter the card number in the Dashboard or in any payment form.
@@ -138,13 +167,15 @@ Use any value you like for other form fields.
138
167
139
168
See more in the [stripe testing documentation](https://stripe.com/docs/testing)
0 commit comments