Skip to content

Commit

Permalink
docs: prettier
Browse files Browse the repository at this point in the history
  • Loading branch information
Topener committed Oct 5, 2023
1 parent e56f08b commit 917cd20
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 1 deletion.
2 changes: 1 addition & 1 deletion docs/commands/d2-cluster.md
Original file line number Diff line number Diff line change
Expand Up @@ -175,7 +175,7 @@ d2 debug cache list clusters/2.40.1
│ config.json │ 205 │ 2023-10-05 06:59:04 │
├────────────────┼──────┼─────────────────────┤
│ docker-compose │ 160 │ 2023-08-09 12:52:24 │
└────────────────┴──────┴─────────────────────┘
└────────────────┴──────┴─────────────────────┘
```

And it looks like this:
Expand Down
2 changes: 2 additions & 0 deletions docs/recipes/stable.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,7 @@ slug: '/cli/recipes/stable-version'
---

# Spin up a stable version

Spinning up a stable version is what you generally want. The Stable version is the one tested and released by the DHIS2 core team. It is the version that is recommended for production use, and therefore also the best to develop on. However, sometimes it makes sense to check out the development branch to test with the latest features. Read more about the [development branch here](./development.md).

First up, in the best case scenario where you want to run DHIS2 v40 on an empty database, you are able to run:
Expand All @@ -26,6 +27,7 @@ Usually you want to `seed` your database with a database dump from Sierra Leone
d2 cluster up 2.40.0 --seed
# fail: if there's no 2.40.0 database dump, it will fail
```

You'll need to provide a `--db-version` argument to tell the command which database dump to use. The database dump needs to exist on the [databases](https://databases.dhis2.org/) site.

```bash
Expand Down

0 comments on commit 917cd20

Please sign in to comment.