Skip to content

feat: testnet deployment #596

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jul 18, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions .vitepress/config.ts
Original file line number Diff line number Diff line change
Expand Up @@ -257,11 +257,15 @@ function sidebarHome() {
items: [
{
text: "Overview",
link: "/guides/deploy-overview",
link: "/guides/deploy/overview",
},
{
text: "Docker Compose",
link: "/guides/docker-compose",
text: "Local (dev)",
link: "/guides/deploy/local",
},
{
text: "Testnet",
link: "/guides/deploy/testnet",
},
],
},
Expand Down
2 changes: 1 addition & 1 deletion guides/deploy-overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,4 +16,4 @@ In this section, you'll see a few examples of how you can deploy your rollup env
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.
:::

* [Deploy with Docker Compose](/guides/docker-compose.md)
* [Deploy with Docker Compose](/guides/deploy/local.md)
16 changes: 8 additions & 8 deletions guides/docker-compose.md → guides/deploy/local.md
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
# 🐳 Docker Compose
# 🏠 Local

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

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

<!-- markdownlint-disable MD033 -->
<script setup>
import Callout from '../.vitepress/components/callout.vue'
import constants from '../.vitepress/constants/constants.js'
import Callout from '../../.vitepress/components/callout.vue'
import constants from '../../.vitepress/constants/constants.js'
</script>

:::tip
Expand Down Expand Up @@ -61,7 +61,7 @@ RUN apt update && \
ca-certificates \
curl

RUN curl -sSL https://rollkit.dev/install.sh | bash
RUN curl -sSL https://rollkit.dev/install.sh | bash
# Install rollkit

# Install ignite
Expand All @@ -71,17 +71,17 @@ RUN curl https://get.ignite.com/cli! | bash
WORKDIR /app

# cache dependencies.
COPY ./go.mod .
COPY ./go.sum .
COPY ./go.mod .
COPY ./go.sum .
RUN go mod download

# Copy all files from the current directory to the container
COPY . .

# Build the chain
RUN ignite app install -g github.com/ignite/apps/rollkit
RUN ignite chain build -y
RUN ignite rollkit init
RUN ignite chain build -y
RUN ignite rollkit init

# Stage 2: Set up the runtime environment
FROM debian:bookworm-slim
Expand Down
47 changes: 47 additions & 0 deletions guides/deploy/overview.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,47 @@
---
description: This page provides an overview of some common ways to deploy rollups.
---

# 🚀 Deploying Your Rollup

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.

You can learn more about Rollkit architecture [here](/learn/specs/overview.md).

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.

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.

## 🏗️ Deployment Scales

Depending on your needs and the stage of your rollup development, there are different deployment approaches you can take:

### 🏠 Local Development
For development and testing purposes, you can deploy your rollup locally using containerized environments. This approach provides:
- Quick iteration and testing
- No external dependencies
- Full control over the environment
- Cost-effective development

### 🌐 Testnet Deployment
When you're ready to test with real network conditions, you can deploy to testnet environments. This includes:
- Integration with testnet DA networks
- Real network latency and conditions
- Multi-node testing scenarios
- Pre-production validation


## 📚 Available Deployment Guides

Choose the deployment approach that matches your current needs:

* [🏠 Local Development with Docker Compose](./local.md) - Deploy locally for development and testing
* [🌐 Testnet Deployment](./testnet.md) - Deploy on testnet with external DA networks

:::warning Disclaimer
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.
:::

## 🎉 Next Steps

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.
Loading