Skip to content

docs: table for provisioning options table #727

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.

Sign up for GitHub

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
peterpeterparker merged 3 commits into from
Apr 21, 2026
Merged

docs: table for provisioning options table #727

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
33b9487
docs: provisioning options table
peterpeterparker Apr 21, 2026
c7cefad
chore: typo
peterpeterparker Apr 21, 2026
9ed75f9
📄 Update LLMs.txt snapshot for PR review
github-actions[bot] Apr 21, 2026
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
24 changes: 22 additions & 2 deletions .llms-snapshots/llms-full.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10178,7 +10178,7 @@ The creation wizard for Satellites and Orbiters includes advanced provisioning o

---

## Hosting Memory
## Website vs Application

When you initialize a satellite, you must decide how the frontend will be kept in memory and served on the web.

Expand All @@ -10202,6 +10202,26 @@ For more background on memory behavior and limits, see the [Memory](/docs/miscel

---

### Summary

The table below summaries the difference regarding the **hosting memory**.

**Note:**

This comparison relates strictly to where your frontend assets (JS, HTML, etc.) are stored and served from.

| | Website (heap) | Application (stable) |
| --- | --- | --- |
| **Best for** | Websites, blogs, content sites | SPAs, feature-rich applications |
| **Speed** | Faster, more consistent | Slightly slower on average, spikier under load |
| **Asset size limit** | ~1 GB (serialization on upgrade) | No practical limit |
| **Upgrade cost** | Assets re-serialized on every upgrade | Assets survive upgrades without re-processing |
| **SEO impact** | Better (lower TTFB, ~0.5 s faster LCP) | Minor overhead (~0.5 s added to CWV) |
| **Default in Console** | ✅ Website | ✅ Application |
| **Can be changed later?** | ✅ Yes — in Hosting › Settings (requires no active files) | ✅ Yes — in Hosting › Settings (requires no active files) |

---

## Selecting a Subnet

If you want more control over where your module is provisioned, you can select a [subnet](/docs/terminology.md#subnet) during the creation process.
Expand Down Expand Up @@ -10688,7 +10708,7 @@ Usage: juno changes reject [options]Options: -i, --id The ID of th
Handle tasks related to the emulator like starting/stopping a local network.

```
Usage: juno emulator <subcommand> [options]Subcommands: clear Clear the local emulator state (volume and container). start Start the emulator for local development. stop Stop the local network. wait Wait until the emulator is ready.
Usage: juno emulator <subcommand> [options]Subcommands: clear Clear the local emulator state (volume and container). pull Pull the latest emulator image. start Start the emulator for local development. stop Stop the local network. wait Wait until the emulator is ready.
```

---
Expand Down
29 changes: 28 additions & 1 deletion docs/miscellaneous/provisioning-options.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,15 @@
---
toc_min_heading_level: 2
toc_max_heading_level: 2
---

# Provisioning Options

The creation wizard for Satellites and Orbiters includes advanced provisioning options for developers who need more control.

---

## Hosting Memory
## Website vs Application

When you initialize a satellite, you must decide how the frontend will be kept in memory and served on the web.

Expand All @@ -30,6 +35,28 @@ For more background on memory behavior and limits, see the [Memory](./memory.md)

---

### Summary

The table below summaries the difference regarding the **hosting memory**.

:::note

This comparison relates strictly to where your frontend assets (JS, HTML, etc.) are stored and served from.

:::

| | Website (heap) | Application (stable) |
| ------------------------- | --------------------------------------------------------- | --------------------------------------------------------- |
| **Best for** | Websites, blogs, content sites | SPAs, feature-rich applications |
| **Speed** | Faster, more consistent | Slightly slower on average, spikier under load |
| **Asset size limit** | ~1 GB (serialization on upgrade) | No practical limit |
| **Upgrade cost** | Assets re-serialized on every upgrade | Assets survive upgrades without re-processing |
| **SEO impact** | Better (lower TTFB, ~0.5 s faster LCP) | Minor overhead (~0.5 s added to CWV) |
| **Default in Console** | ✅ Website | ✅ Application |
| **Can be changed later?** | ✅ Yes — in Hosting › Settings (requires no active files) | ✅ Yes — in Hosting › Settings (requires no active files) |

---

## Selecting a Subnet

If you want more control over where your module is provisioned, you can select a [subnet] during the creation process.
Expand Down
Loading