Skip to content

Commit 3d14f73

Browse files
committed
feat: testnet deployment
1 parent dda588f commit 3d14f73

File tree

5 files changed

+351
-12
lines changed

5 files changed

+351
-12
lines changed

.vitepress/config.ts

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -257,11 +257,15 @@ function sidebarHome() {
257257
items: [
258258
{
259259
text: "Overview",
260-
link: "/guides/deploy-overview",
260+
link: "/guides/deploy/overview",
261261
},
262262
{
263-
text: "Docker Compose",
264-
link: "/guides/docker-compose",
263+
text: "Local (dev)",
264+
link: "/guides/deploy/local",
265+
},
266+
{
267+
text: "Testnet",
268+
link: "/guides/deploy/testnet",
265269
},
266270
],
267271
},

guides/deploy-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,4 +16,4 @@ In this section, you'll see a few examples of how you can deploy your rollup env
1616
These examples are for educational purposes only. Before deploying your rollup for production use you should fully understand the services you are deploying and your choice in deployment method.
1717
:::
1818

19-
* [Deploy with Docker Compose](/guides/docker-compose.md)
19+
* [Deploy with Docker Compose](/guides/deploy/local.md)

guides/docker-compose.md renamed to guides/deploy/local.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
1-
# 🐳 Docker Compose
1+
# 🏠 Local
22

33
This tutorial is going to show you how to deploy the [gm-world chain](/guides/gm-world.md) using Docker Compose.
44

55
You can learn more about Docker Compose [here](https://docs.docker.com/compose/).
66

77
<!-- markdownlint-disable MD033 -->
88
<script setup>
9-
import Callout from '../.vitepress/components/callout.vue'
10-
import constants from '../.vitepress/constants/constants.js'
9+
import Callout from '../../.vitepress/components/callout.vue'
10+
import constants from '../../.vitepress/constants/constants.js'
1111
</script>
1212

1313
:::tip
@@ -61,7 +61,7 @@ RUN apt update && \
6161
ca-certificates \
6262
curl
6363
64-
RUN curl -sSL https://rollkit.dev/install.sh | bash
64+
RUN curl -sSL https://rollkit.dev/install.sh | bash
6565
# Install rollkit
6666
6767
# Install ignite
@@ -71,17 +71,17 @@ RUN curl https://get.ignite.com/cli! | bash
7171
WORKDIR /app
7272
7373
# cache dependencies.
74-
COPY ./go.mod .
75-
COPY ./go.sum .
74+
COPY ./go.mod .
75+
COPY ./go.sum .
7676
RUN go mod download
7777
7878
# Copy all files from the current directory to the container
7979
COPY . .
8080
8181
# Build the chain
8282
RUN ignite app install -g github.com/ignite/apps/rollkit
83-
RUN ignite chain build -y
84-
RUN ignite rollkit init
83+
RUN ignite chain build -y
84+
RUN ignite rollkit init
8585
8686
# Stage 2: Set up the runtime environment
8787
FROM debian:bookworm-slim

guides/deploy/overview.md

Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
---
2+
description: This page provides an overview of some common ways to deploy rollups.
3+
---
4+
5+
# 🚀 Deploying Your Rollup
6+
7+
One of the benefits of building rollups with Rollkit is the flexibility you have as a developer to choose things like the DA layer, the settlement scheme, and the execution environment.
8+
9+
You can learn more about Rollkit architecture [here](/learn/stack.md).
10+
11+
The challenge that comes with this flexibility is that there are more services that now need to be deployed and managed while running your rollup.
12+
13+
In the tutorials so far, you've seen various helper scripts used to make things easier. While great for tutorials, there are better ways to deploy and manage rollups than using various bash scripts.
14+
15+
## 🏗️ Deployment Scales
16+
17+
Depending on your needs and the stage of your rollup development, there are different deployment approaches you can take:
18+
19+
### 🏠 Local Development
20+
For development and testing purposes, you can deploy your rollup locally using containerized environments. This approach provides:
21+
- Quick iteration and testing
22+
- No external dependencies
23+
- Full control over the environment
24+
- Cost-effective development
25+
26+
### 🌐 Testnet Deployment
27+
When you're ready to test with real network conditions, you can deploy to testnet environments. This includes:
28+
- Integration with testnet DA networks
29+
- Real network latency and conditions
30+
- Multi-node testing scenarios
31+
- Pre-production validation
32+
33+
34+
## 📚 Available Deployment Guides
35+
36+
Choose the deployment approach that matches your current needs:
37+
38+
* [🏠 Local Development with Docker Compose](./local.md) - Deploy locally for development and testing
39+
* [🌐 Testnet Deployment](./testnet.md) - Deploy on testnet with external DA networks
40+
41+
:::warning Disclaimer
42+
These examples are for educational purposes only. Before deploying your rollup for production use you should fully understand the services you are deploying and your choice in deployment method.
43+
:::
44+
45+
## 🎉 Next Steps
46+
47+
For production mainnet deployments, consider additional requirements such as monitoring, security audits, infrastructure hardening, and operational procedures that go beyond the scope of these tutorials.

0 commit comments

Comments
 (0)