Skip to content

Commit 303cb7e

Browse files
docs: table for provisioning options table (#727)
* docs: provisioning options table Signed-off-by: David Dal Busco <david.dalbusco@outlook.com> * chore: typo Signed-off-by: David Dal Busco <david.dalbusco@outlook.com> * 📄 Update LLMs.txt snapshot for PR review --------- Signed-off-by: David Dal Busco <david.dalbusco@outlook.com> Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
1 parent 5ba7fc1 commit 303cb7e

2 files changed

Lines changed: 50 additions & 3 deletions

File tree

‎.llms-snapshots/llms-full.txt‎

Lines changed: 22 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10178,7 +10178,7 @@ The creation wizard for Satellites and Orbiters includes advanced provisioning o
1017810178

1017910179
---
1018010180

10181-
## Hosting Memory
10181+
## Website vs Application
1018210182

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

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

1020310203
---
1020410204

10205+
### Summary
10206+
10207+
The table below summaries the difference regarding the **hosting memory**.
10208+
10209+
**Note:**
10210+
10211+
This comparison relates strictly to where your frontend assets (JS, HTML, etc.) are stored and served from.
10212+
10213+
| | Website (heap) | Application (stable) |
10214+
| --- | --- | --- |
10215+
| **Best for** | Websites, blogs, content sites | SPAs, feature-rich applications |
10216+
| **Speed** | Faster, more consistent | Slightly slower on average, spikier under load |
10217+
| **Asset size limit** | ~1 GB (serialization on upgrade) | No practical limit |
10218+
| **Upgrade cost** | Assets re-serialized on every upgrade | Assets survive upgrades without re-processing |
10219+
| **SEO impact** | Better (lower TTFB, ~0.5 s faster LCP) | Minor overhead (~0.5 s added to CWV) |
10220+
| **Default in Console** | ✅ Website | ✅ Application |
10221+
| **Can be changed later?** | ✅ Yes — in Hosting › Settings (requires no active files) | ✅ Yes — in Hosting › Settings (requires no active files) |
10222+
10223+
---
10224+
1020510225
## Selecting a Subnet
1020610226

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

1069010710
```
10691-
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.
10711+
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.
1069210712
```
1069310713

1069410714
---

‎docs/miscellaneous/provisioning-options.mdx‎

Lines changed: 28 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,15 @@
1+
---
2+
toc_min_heading_level: 2
3+
toc_max_heading_level: 2
4+
---
5+
16
# Provisioning Options
27

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

510
---
611

7-
## Hosting Memory
12+
## Website vs Application
813

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

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

3136
---
3237

38+
### Summary
39+
40+
The table below summaries the difference regarding the **hosting memory**.
41+
42+
:::note
43+
44+
This comparison relates strictly to where your frontend assets (JS, HTML, etc.) are stored and served from.
45+
46+
:::
47+
48+
| | Website (heap) | Application (stable) |
49+
| ------------------------- | --------------------------------------------------------- | --------------------------------------------------------- |
50+
| **Best for** | Websites, blogs, content sites | SPAs, feature-rich applications |
51+
| **Speed** | Faster, more consistent | Slightly slower on average, spikier under load |
52+
| **Asset size limit** | ~1 GB (serialization on upgrade) | No practical limit |
53+
| **Upgrade cost** | Assets re-serialized on every upgrade | Assets survive upgrades without re-processing |
54+
| **SEO impact** | Better (lower TTFB, ~0.5 s faster LCP) | Minor overhead (~0.5 s added to CWV) |
55+
| **Default in Console** | ✅ Website | ✅ Application |
56+
| **Can be changed later?** | ✅ Yes — in Hosting › Settings (requires no active files) | ✅ Yes — in Hosting › Settings (requires no active files) |
57+
58+
---
59+
3360
## Selecting a Subnet
3461

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

0 commit comments

Comments
 (0)