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: docs/guides/local-development.mdx
+23-4Lines changed: 23 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,26 @@
1
1
---
2
2
id: local-development
3
3
title: Local Development
4
-
description: Set-up the local emulator with Docker or Podman
4
+
description: Run a full local development environment with the Juno emulator using Docker or Podman, complete with Console UI, live reload, and smart contract support.
5
5
---
6
6
7
7
# Local Development
8
8
9
9
Juno offers something most platforms don’t: a full local development environment that closely mirrors production.
When you develop locally, you're running an emulator that includes the well known infrastructure services — including the actual administration Console UI.
12
25
13
26
This enables:
@@ -22,9 +35,9 @@ This enables:
22
35
23
36
## Before you begin
24
37
25
-
An emulator — a self-contained local environment that includes services, replicas, and the Console UI — is run using containers. You can use [Docker](https://www.docker.com/)(default) or [Podman](https://podman.io/)as the container runtime.
38
+
The emulator is a self-contained local environment that runs in a container managed entirely by Juno — using either [Docker](https://www.docker.com/) or [Podman](https://podman.io/)under the hood.
26
39
27
-
Make sure either tool is installed on your machine:
40
+
Make sure your preferred runtime is installed on your machine:
@@ -43,7 +56,7 @@ For **Podman**, we are not aware of any particular version requirements at this
43
56
44
57
## Getting Started
45
58
46
-
The easiest way to run the local developer environment is through the CLI.
59
+
To run the emulator for local development, you need to have the Juno CLI installed.
47
60
48
61
If you haven’t installed it yet, run:
49
62
@@ -67,6 +80,12 @@ To stop the emulator, run:
67
80
juno dev stop
68
81
```
69
82
83
+
:::note
84
+
85
+
While you could technically start the emulator using `docker run` or `podman run`, we recommend using the Juno CLI to manage the emulator lifecycle. It handles important checks, sets the correct configuration, and ensures everything runs as expected.
0 commit comments