From f1d7d51170ca4ae457a9325074084e9460a18a41 Mon Sep 17 00:00:00 2001 From: David Dal Busco Date: Wed, 7 Jan 2026 09:38:04 +0100 Subject: [PATCH 1/2] docs: capitalize segments' names Signed-off-by: David Dal Busco --- docs/build/analytics/index.md | 8 ++++---- docs/build/authentication/internet-identity.md | 6 +++--- docs/build/components/encoding.mdx | 2 +- docs/build/components/http-headers.mdx | 2 +- docs/build/components/ignore-files.mdx | 2 +- docs/build/components/source.mdx | 4 ++-- docs/build/datastore/collections.md | 6 +++--- docs/build/datastore/development.mdx | 4 ++-- docs/build/datastore/index.mdx | 2 +- .../build/functions/development/components/on-init.mdx | 4 ++-- .../development/components/on-post-upgrade.mdx | 2 +- docs/build/functions/index.md | 4 ++-- docs/build/hosting/configuration.mdx | 2 +- docs/build/hosting/development.md | 2 +- docs/build/hosting/index.md | 2 +- docs/build/storage/collections.md | 6 +++--- docs/build/storage/index.mdx | 4 ++-- docs/create-a-satellite.mdx | 10 +++++----- docs/guides/ai.md | 2 +- docs/guides/angular/deploy.mdx | 2 +- docs/guides/astro/deploy.mdx | 2 +- docs/guides/docusaurus/deploy.mdx | 2 +- docs/guides/github-actions/deploy-frontend.mdx | 2 +- docs/guides/github-actions/index.mdx | 8 ++++---- docs/guides/react/deploy.mdx | 2 +- docs/miscellaneous/access-keys.md | 4 ++-- docs/pricing.md | 8 ++++---- docs/reference/cli.mdx | 6 +++--- docs/reference/configuration.mdx | 2 +- docs/setup-the-sdk.mdx | 2 +- docs/terminology.md | 10 +++++----- docs/troubleshooting.md | 4 ++-- 32 files changed, 64 insertions(+), 64 deletions(-) diff --git a/docs/build/analytics/index.md b/docs/build/analytics/index.md index d9e57a1f..22fa8242 100644 --- a/docs/build/analytics/index.md +++ b/docs/build/analytics/index.md @@ -69,7 +69,7 @@ All tracked data is securely stored on the [Internet Computer](https://internetc ### No cross-dapp tracking -Juno Analytics does not follow users across websites and applications they visit. All data remains isolated to a single satellite. +Juno Analytics does not follow users across websites and applications they visit. All data remains isolated to a single Satellite. ### You 100% own your data @@ -83,7 +83,7 @@ You have the capability to delete all collected data within your Analytics at an To gather analytics for your dapps, you need to create an [orbiter]. Creating an Orbiter requires ICP, and its price is defined in the [transaction costs](../../pricing#transaction-costs). -Each orbiter is used to collect analytics for one or multiple [satellites]. +Each Orbiter is used to collect analytics for one or multiple [satellites]. Page views are collected anonymously and saved with a unique random ID for attribution. This data is organized based on its collection timestamp. @@ -95,11 +95,11 @@ Additionally, a unique random session ID is generated for all data. Each time a ## Limitation -Currently, an orbiter can store up to 500 GB of data. +Currently, an Orbiter can store up to 500 GB of data. :::caution -Similar to other analytics services, an Orbiter accepts data submitted from any source as long as the requested payload matches the expected format, and the targeted satellite is configured to accept analytics. This is because the origin of the HTTP request cannot be accessed, for a valid reason – to prevent tracking. Therefore, calls cannot be limited to the domain of your dapps. +Similar to other analytics services, an Orbiter accepts data submitted from any source as long as the requested payload matches the expected format, and the targeted Satellite is configured to accept analytics. This is because the origin of the HTTP request cannot be accessed, for a valid reason – to prevent tracking. Therefore, calls cannot be limited to the domain of your dapps. Consequently, this leaves the canister open to potential attacks that can pollute the data and consume cycles. For this reason, we recommend the following: diff --git a/docs/build/authentication/internet-identity.md b/docs/build/authentication/internet-identity.md index bdf82e96..7f57d856 100644 --- a/docs/build/authentication/internet-identity.md +++ b/docs/build/authentication/internet-identity.md @@ -7,7 +7,7 @@ keywords: [Internet Identity, decentralized authentication, Internet Computer] [Internet Identity](https://identity.ic0.app) lets users authenticate securely and anonymously through a decentralized identity system built for the Internet Computer. -When a user signs in with Internet Identity, they confirm their identity through the provider. If successful, a session is created automatically and the user can interact with your satellite. +When a user signs in with Internet Identity, they confirm their identity through the provider. If successful, a session is created automatically and the user can interact with your Satellite. Authentication with Internet Identity offers strong privacy guarantees and complete isolation between domains by design. @@ -46,7 +46,7 @@ Internet Identity sign-in can be customized with options that let you control se | ---------------------------- | ---------------------------------------------- | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `maxTimeToLiveInNanoseconds` | `BigInt(4 * 60 * 60 * 1000 * 1000 * 1000)` | **4 hours** | Maximum lifetime of the user's session in **nanoseconds**. Once expired, the session cannot be extended. | | `windowed` | `boolean` | `true` | By default, the authentication flow is presented in a popup window on desktop that is automatically centered on the browser. This behavior can be turned off by setting the option to `false`, causing the authentication flow to happen in a separate tab instead. | -| `derivationOrigin` | `string` or `URL` | | The main domain to be used to ensure your users are identified with the same public ID, regardless of which of your satellite's URLs they use to access your application. | +| `derivationOrigin` | `string` or `URL` | | The main domain to be used to ensure your users are identified with the same public ID, regardless of which of your Satellite's URLs they use to access your application. | | `onProgress` | `(progress) => void` | | Callback for provider sign-in and user creation/loading. | | `domain` | `internetcomputer.org` or `ic0.app` or `id.ai` | `internetcomputer.org` | The domain on which to open Internet Identity. | @@ -141,6 +141,6 @@ If you're unsure which domain to use as the primary domain, here are two common - Alternatively, stick with **the default domain** (`{satellite-id}.icp0.io`) if: - You're still experimenting with your domain setup and might change it later. - You're not ready to commit to a long-term domain. - - You plan to host multiple satellites under different domains and don't want to tie user identity to just one. + - You plan to host multiple Satellites under different domains and don't want to tie user identity to just one. Choosing the right derivation origin early helps avoid identity issues later, but both approaches are valid depending on your goals. diff --git a/docs/build/components/encoding.mdx b/docs/build/components/encoding.mdx index dc60c0fd..c4b120c0 100644 --- a/docs/build/components/encoding.mdx +++ b/docs/build/components/encoding.mdx @@ -1,4 +1,4 @@ -When deploying, the CLI automatically maps the encoding type based on the file extension. The encoding information is then used in the satellite to provide the appropriate HTTP response header `Content-Encoding`. +When deploying, the CLI automatically maps the encoding type based on the file extension. The encoding information is then used in the Satellite to provide the appropriate HTTP response header `Content-Encoding`. The default mappings are as follows: diff --git a/docs/build/components/http-headers.mdx b/docs/build/components/http-headers.mdx index 1494600e..66746f26 100644 --- a/docs/build/components/http-headers.mdx +++ b/docs/build/components/http-headers.mdx @@ -1,4 +1,4 @@ -Headers allow the client and the satellite to pass additional information along with a request or a response. Some sets of headers can affect how the browser handles the page and its content. +Headers allow the client and the Satellite to pass additional information along with a request or a response. Some sets of headers can affect how the browser handles the page and its content. For instance, you may want to set a specific `Cache-Control` for performance reasons. diff --git a/docs/build/components/ignore-files.mdx b/docs/build/components/ignore-files.mdx index 0247dcb4..4fdad173 100644 --- a/docs/build/components/ignore-files.mdx +++ b/docs/build/components/ignore-files.mdx @@ -1,4 +1,4 @@ -The `ignore` attribute allows you to exclude certain files from being deployed to your satellite. +The `ignore` attribute allows you to exclude certain files from being deployed to your Satellite. This attribute works similarly to Git's `.gitignore`, and you can specify which files to ignore using globs. diff --git a/docs/build/components/source.mdx b/docs/build/components/source.mdx index 147abb38..be4c83d7 100644 --- a/docs/build/components/source.mdx +++ b/docs/build/components/source.mdx @@ -1,10 +1,10 @@ -The `source` field specifies the directory that contains the built assets for your satellite. This is typically the output directory generated by your build process after running a command like `npm run build`. +The `source` field specifies the directory that contains the built assets for your Satellite. This is typically the output directory generated by your build process after running a command like `npm run build`. import Examples from "./source-examples.mdx"; -Juno uses this directory to locate the files that will be deployed as part of your satellite. Ensure that this directory includes all the necessary assets, such as HTML, JavaScript, CSS, and any other static or dynamic resources your application requires. +Juno uses this directory to locate the files that will be deployed as part of your Satellite. Ensure that this directory includes all the necessary assets, such as HTML, JavaScript, CSS, and any other static or dynamic resources your application requires. ```javascript title="juno.config.js" import { defineConfig } from "@junobuild/config"; diff --git a/docs/build/datastore/collections.md b/docs/build/datastore/collections.md index 9094eeb2..bb16e492 100644 --- a/docs/build/datastore/collections.md +++ b/docs/build/datastore/collections.md @@ -28,9 +28,9 @@ Permissions define who can read and write documents in a collection. Writing inc | Permission | Description | | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Public** | Anyone can read or write documents in the collection. | -| **Private** | Only the creator (owner) of a document can read or write to it. However, note that since satellite administrators manage the underlying infrastructure, they have the technical ability to modify access rules by changing its source code. | -| **Managed** | The owner of a document, the administrator and editor of the satellite can read or write to it in the collection. | -| **Restricted** | Only satellite administrator and editor can read or write any document in the collection. | +| **Private** | Only the creator (owner) of a document can read or write to it. However, note that since Satellite administrators manage the underlying infrastructure, they have the technical ability to modify access rules by changing its source code. | +| **Managed** | The owner of a document, the administrator and editor of the Satellite can read or write to it in the collection. | +| **Restricted** | Only Satellite administrator and editor can read or write any document in the collection. | If not set to immutable, you can modify the permissions at any time, and the changes will take effect immediately. diff --git a/docs/build/datastore/development.mdx b/docs/build/datastore/development.mdx index 927120c3..fb8fd526 100644 --- a/docs/build/datastore/development.mdx +++ b/docs/build/datastore/development.mdx @@ -129,7 +129,7 @@ await setDoc({ }); ``` -The `version` must match the current version of the last document within the satellite; otherwise, the call will fail. This prevents unexpected concurrent overwrites, which is useful, for example, if your users use your projects simultaneously on multiple devices. +The `version` must match the current version of the last document within the Satellite; otherwise, the call will fail. This prevents unexpected concurrent overwrites, which is useful, for example, if your users use your projects simultaneously on multiple devices. :::tip @@ -387,7 +387,7 @@ await deleteDoc({ }); ``` -The document must include the current `version` from the latest entry within the satellite; otherwise, the call will fail. This prevents unexpected concurrent overwrites, which is particularly useful if your users access your projects simultaneously on multiple devices. +The document must include the current `version` from the latest entry within the Satellite; otherwise, the call will fail. This prevents unexpected concurrent overwrites, which is particularly useful if your users access your projects simultaneously on multiple devices. ### Delete multiple documents diff --git a/docs/build/datastore/index.mdx b/docs/build/datastore/index.mdx index 3aeafbe3..9906b193 100644 --- a/docs/build/datastore/index.mdx +++ b/docs/build/datastore/index.mdx @@ -38,7 +38,7 @@ In essence, a "Datastore" functions as a keypair store. ## Limitation -Each satellite has specific memory limits. For detailed information, please refer to the related [documentation](../../miscellaneous/memory.md) page. +Each Satellite has specific memory limits. For detailed information, please refer to the related [documentation](../../miscellaneous/memory.md) page. As for documents, they can be up to 2MB in size. However, larger files can be saved in the [storage](build/storage/index.mdx). diff --git a/docs/build/functions/development/components/on-init.mdx b/docs/build/functions/development/components/on-init.mdx index de0ecbf8..3cc532e7 100644 --- a/docs/build/functions/development/components/on-init.mdx +++ b/docs/build/functions/development/components/on-init.mdx @@ -8,8 +8,8 @@ import styles from "./styles.module.scss"; ```

- Called during the initialization of the satellite. This hook is invoked when - the satellite is first deployed and can be used to set up initial + Called during the initialization of the Satellite. This hook is invoked when + the Satellite is first deployed and can be used to set up initial configurations or resources.

diff --git a/docs/build/functions/development/components/on-post-upgrade.mdx b/docs/build/functions/development/components/on-post-upgrade.mdx index e253f918..adba7fd4 100644 --- a/docs/build/functions/development/components/on-post-upgrade.mdx +++ b/docs/build/functions/development/components/on-post-upgrade.mdx @@ -8,7 +8,7 @@ import styles from "./styles.module.scss"; ```

- Invoked after the satellite has been upgraded to a new version. This hook is + Invoked after the Satellite has been upgraded to a new version. This hook is typically used to manage migration tasks, or starting custom processes like timers.

diff --git a/docs/build/functions/index.md b/docs/build/functions/index.md index 834ede87..6fb5d137 100644 --- a/docs/build/functions/index.md +++ b/docs/build/functions/index.md @@ -55,8 +55,8 @@ Custom hooks are not active by default. You need to opt in to enable event-drive | `on_delete_asset` | Storage | Activated when an asset is deleted. | | `on_delete_many_assets` | Storage | Used for deleting multiple assets. | | `on_delete_filtered_assets` | Storage | Invoked when assets are deleted based on filters. | -| `on_init` | Satellite | Called during the initialization of the satellite. | -| `on_post_upgrade` | Satellite | Invoked after the satellite has been upgraded to a new version. | +| `on_init` | Satellite | Called during the initialization of the Satellite. | +| `on_post_upgrade` | Satellite | Invoked after the Satellite has been upgraded to a new version. | --- diff --git a/docs/build/hosting/configuration.mdx b/docs/build/hosting/configuration.mdx index f17bee83..a3f0538e 100644 --- a/docs/build/hosting/configuration.mdx +++ b/docs/build/hosting/configuration.mdx @@ -53,7 +53,7 @@ import HttpHeaders from "../components/http-headers.mdx"; By default, all unknown paths are automatically rewritten to `/index.html`. However, if you wish to serve a custom `404 Not Found` error when a user attempts to access a non-existent page, you can do so without requiring additional configuration. -Simply upload a custom `404.html` file to your satellite that should be served from the root path of your site. +Simply upload a custom `404.html` file to your Satellite that should be served from the root path of your site. ### Redirects diff --git a/docs/build/hosting/development.md b/docs/build/hosting/development.md index e90834f8..4ea26dee 100644 --- a/docs/build/hosting/development.md +++ b/docs/build/hosting/development.md @@ -9,7 +9,7 @@ This section covers how to configure and manage your custom domain in Juno, incl To connect your custom domain, follow these steps: 1. Start the custom domain wizard from the Juno console [hosting](https://console.juno.build/hosting) page -2. Enter the desired domain name for your satellite +2. Enter the desired domain name for your Satellite 3. Log into your domain provider's site and configure the DNS records as indicated by Juno 4. Continue the process in Juno diff --git a/docs/build/hosting/index.md b/docs/build/hosting/index.md index 1d699f54..e05a09eb 100644 --- a/docs/build/hosting/index.md +++ b/docs/build/hosting/index.md @@ -14,7 +14,7 @@ keywords: Juno Hosting makes it easy to put your project online: fast, secure, and reliable by default. -Deploy your web applications or static sites directly to a satellite using [GitHub Actions](../../guides/github-actions/index.mdx). Your builds run automatically, so shipping updates feels as simple as pushing code. +Deploy your web applications or static sites directly to a Satellite using [GitHub Actions](../../guides/github-actions/index.mdx). Your builds run automatically, so shipping updates feels as simple as pushing code. Prefer running things locally? You can also use the [CLI](../../guides/manual-deployment.mdx). diff --git a/docs/build/storage/collections.md b/docs/build/storage/collections.md index a01d7166..669c13c9 100644 --- a/docs/build/storage/collections.md +++ b/docs/build/storage/collections.md @@ -34,9 +34,9 @@ Assets are publicly accessible on the Internet regardless of the permission sche | Permission | Description | | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Public** | Anyone can read or write assets in the collection. | -| **Private** | Only the creator (owner) of the asset can read or write to it. However, note that since satellite administrators manage the underlying infrastructure, they have the technical ability to modify access rules by changing its source code. | -| **Managed** | The owner of an asset, the administrator and editor of the satellite can read or write to it in the collection. | -| **Restricted** | Only satellite administrator and editor can read or write any asset in the collection. | +| **Private** | Only the creator (owner) of the asset can read or write to it. However, note that since Satellite administrators manage the underlying infrastructure, they have the technical ability to modify access rules by changing its source code. | +| **Managed** | The owner of an asset, the administrator and editor of the Satellite can read or write to it in the collection. | +| **Restricted** | Only Satellite administrator and editor can read or write any asset in the collection. | If not set to immutable, you can modify the permissions at any time, and the changes will take effect immediately. diff --git a/docs/build/storage/index.mdx b/docs/build/storage/index.mdx index 9c2047f7..64bfa524 100644 --- a/docs/build/storage/index.mdx +++ b/docs/build/storage/index.mdx @@ -31,7 +31,7 @@ Those assets hold the data you want to persist on chain, along with metadata (th :::caution -Unless you use the optional [`token` parameter](development.mdx#protected-asset) to persist an asset in your satellite and make its URL difficult to guess, any asset stored in Juno Storage will be publicly available on the internet. +Unless you use the optional [`token` parameter](development.mdx#protected-asset) to persist an asset in your Satellite and make its URL difficult to guess, any asset stored in Juno Storage will be publicly available on the internet. ::: @@ -39,7 +39,7 @@ Unless you use the optional [`token` parameter](development.mdx#protected-asset) ## Limitation -Each satellite has specific memory limits. For detailed information, please refer to the related [documentation](../../miscellaneous/memory.md) page. +Each Satellite has specific memory limits. For detailed information, please refer to the related [documentation](../../miscellaneous/memory.md) page. There is no specific limit on the size of assets (files) that can be uploaded to Juno, unless you choose to set an optional [rule](./collections.md#permissions) to restrict it. diff --git a/docs/create-a-satellite.mdx b/docs/create-a-satellite.mdx index e34bbd53..fc5ac014 100644 --- a/docs/create-a-satellite.mdx +++ b/docs/create-a-satellite.mdx @@ -2,14 +2,14 @@ description: "A quick guide to creating a Satellite on Juno in production — the container that powers your app." keywords: [ - create a satellite, + create a Satellite, deploy with Juno, Juno Satellite, Juno container, Internet Identity, Juno production guide, Juno app deployment, - launch satellite, + launch Satellite, Juno hosting ] --- @@ -19,10 +19,10 @@ keywords: When you're ready to deploy your project to production, you'll need to create a [satellite]. 1. To get started, sign-in to the Juno [console](https://console.juno.build). If you are a new developer on Juno and the Internet Computer, you may be prompted to create your first anonymous [Internet Identity]. -2. Click **Launch a new satellite**. -3. Enter a name for your satellite (note: this is for display purposes only and does not need to be unique). +2. Click **Launch a new Satellite**. +3. Enter a name for your Satellite (note: this is for display purposes only and does not need to be unique). 4. Confirm with **Create a Satellite.** -5. The platform will then create your satellite and provision its resources. +5. The platform will then create your Satellite and provision its resources. 6. Once the process is complete, click **Continue** to access the overview page. 🎉 You’re all set! You can now deploy your frontend app, static website, or publish your serverless functions to production. diff --git a/docs/guides/ai.md b/docs/guides/ai.md index 22a9540c..77ebf794 100644 --- a/docs/guides/ai.md +++ b/docs/guides/ai.md @@ -1,7 +1,7 @@ --- id: ai title: AI -description: Learn how to use Juno's llms.txt files to provide AI tools with better context for building serverless functions, deploying satellites, and integrating the SDK. +description: Learn how to use Juno's llms.txt files to provide AI tools with better context for building serverless functions, deploying Satellites, and integrating the SDK. --- # Using Juno with AI diff --git a/docs/guides/angular/deploy.mdx b/docs/guides/angular/deploy.mdx index 392b58e5..0147b587 100644 --- a/docs/guides/angular/deploy.mdx +++ b/docs/guides/angular/deploy.mdx @@ -1,6 +1,6 @@ --- sidebar_label: Deploy -description: Learn how to deploy your Angular project to Juno. Follow the deployment guide to configure static exports, set up your satellite, and publish your site to production. +description: Learn how to deploy your Angular project to Juno. Follow the deployment guide to configure static exports, set up your Satellite, and publish your site to production. keywords: [Juno, Angular, integration, quickstart, guide, build, SDK, emulator] toc_min_heading_level: 2 toc_max_heading_level: 2 diff --git a/docs/guides/astro/deploy.mdx b/docs/guides/astro/deploy.mdx index f344af60..426eef39 100644 --- a/docs/guides/astro/deploy.mdx +++ b/docs/guides/astro/deploy.mdx @@ -1,6 +1,6 @@ --- sidebar_label: Deploy -description: Learn how to deploy your Astro project to Juno. Follow the deployment guide to configure static exports, set up your satellite, and publish your site to production. +description: Learn how to deploy your Astro project to Juno. Follow the deployment guide to configure static exports, set up your Satellite, and publish your site to production. keywords: [Juno, Astro, integration, quickstart, guide, build, SDK, emulator] toc_min_heading_level: 2 toc_max_heading_level: 2 diff --git a/docs/guides/docusaurus/deploy.mdx b/docs/guides/docusaurus/deploy.mdx index 0ddaf4bb..8c62d0ae 100644 --- a/docs/guides/docusaurus/deploy.mdx +++ b/docs/guides/docusaurus/deploy.mdx @@ -1,6 +1,6 @@ --- sidebar_label: Deploy -description: Learn how to deploy your Docusaurus project to Juno. Follow the deployment guide to configure static exports, set up your satellite, and publish your site to production. +description: Learn how to deploy your Docusaurus project to Juno. Follow the deployment guide to configure static exports, set up your Satellite, and publish your site to production. keywords: [Juno, Docusaurus, integration, quickstart, guide, build, SDK, emulator] toc_min_heading_level: 2 diff --git a/docs/guides/github-actions/deploy-frontend.mdx b/docs/guides/github-actions/deploy-frontend.mdx index 3fc7b4ef..f6f377f6 100644 --- a/docs/guides/github-actions/deploy-frontend.mdx +++ b/docs/guides/github-actions/deploy-frontend.mdx @@ -69,7 +69,7 @@ Below are key considerations to ensure efficient and cost-effective deployment o ### Build Reproducibility -Only new resources will be deployed to your satellite. Changes are detected through sha256 comparison. Therefore, ensuring the build reproducibility of your application is crucial to accurately identify and deploy the necessary updates. +Only new resources will be deployed to your Satellite. Changes are detected through sha256 comparison. Therefore, ensuring the build reproducibility of your application is crucial to accurately identify and deploy the necessary updates. ### Deployment Costs diff --git a/docs/guides/github-actions/index.mdx b/docs/guides/github-actions/index.mdx index 52ac65e8..010e8d12 100644 --- a/docs/guides/github-actions/index.mdx +++ b/docs/guides/github-actions/index.mdx @@ -20,8 +20,8 @@ Before you can effectively implement automation, it is necessary to add a secret Follow the steps below to generate a new controller: 1. Go to the Juno's [console](https://console.juno.build). -2. Select your satellite. -3. On the satellite's dashboard, navigate to the "Setup" tab. +2. Select your Satellite. +3. On the Satellite's dashboard, navigate to the "Setup" tab. 4. Click on "Add an access key". 5. Generate a new key (default option) and assign it an appropriate role based on your workflow. [Learn more about the available roles and their permissions](../../miscellaneous/access-keys.md) to choose the appropriate level of access for your use case. 6. Click "Submit". @@ -41,8 +41,8 @@ The configuration file can be a TypeScript, JavaScript, or JSON file (`juno.conf At a minimum, the configuration file must include the following: -- **Satellite ID**: A unique identifier for your satellite. -- **Source**: The directory containing the built assets for your satellite. This is typically the output folder of your build process, generated after running a command like `npm run build`. +- **Satellite ID**: A unique identifier for your Satellite. +- **Source**: The directory containing the built assets for your Satellite. This is typically the output folder of your build process, generated after running a command like `npm run build`. ### Satellite ID diff --git a/docs/guides/react/deploy.mdx b/docs/guides/react/deploy.mdx index 7b6a7aa7..be0a8a80 100644 --- a/docs/guides/react/deploy.mdx +++ b/docs/guides/react/deploy.mdx @@ -1,6 +1,6 @@ --- sidebar_label: Deploy -description: Learn how to deploy your React project to Juno. Follow the deployment guide to configure static exports, set up your satellite, and publish your site to production. +description: Learn how to deploy your React project to Juno. Follow the deployment guide to configure static exports, set up your Satellite, and publish your site to production. keywords: [Juno, React, integration, quickstart, guide, build, SDK, emulator] toc_min_heading_level: 2 toc_max_heading_level: 2 diff --git a/docs/miscellaneous/access-keys.md b/docs/miscellaneous/access-keys.md index e481a53b..25e4c6e7 100644 --- a/docs/miscellaneous/access-keys.md +++ b/docs/miscellaneous/access-keys.md @@ -10,7 +10,7 @@ When you sign in to Juno's [Console] using [Internet Identity](https://internetc ![Juno's console flow](../img/console.png) -When you create a [satellite], you and your mission control become its owners. Per extension, you — and no one else (including not Juno) — own your satellite. +When you create a [satellite], you and your Mission Control become its owners. Per extension, you — and no one else (including not Juno) — own your satellite. :::note @@ -31,7 +31,7 @@ Each access key is assigned a **role** that defines what it can do: | **Write** | Editor | ✅ | ✅ | ✅ | ❌ | | **Submit** | Submitter | ✅ | ❌ | ❌ | ❌ | -An **administrator** can perform tasks such as configuring or deploying an app, topping up a mission control or satellite, creating a new collection in the [datastore](../build/datastore/index.mdx) or [storage](../build/storage/index.mdx), or configuring a custom domain in the [hosting](../build/hosting/index.md). +An **administrator** can perform tasks such as configuring or deploying an app, topping up a Mission Control or satellite, creating a new collection in the [datastore](../build/datastore/index.mdx) or [storage](../build/storage/index.mdx), or configuring a custom domain in the [hosting](../build/hosting/index.md). An **editor** can publish new serverless function versions to a Satellite’s CDN, deploy your frontend application, and read data from a collection. However, it cannot directly upgrade a Satellite or start/stop a module. diff --git a/docs/pricing.md b/docs/pricing.md index 8286813f..70fb3c52 100644 --- a/docs/pricing.md +++ b/docs/pricing.md @@ -28,7 +28,7 @@ From there, you can dive into the details below to estimate storage, deployment, ## Operating costs -As the owner of your mission control, satellites and orbiters, you are responsible for their operating costs. +As the owner of your Mission Control, Satellites and Orbiters, you are responsible for their operating costs. To ensure that your infrastructure usage is covered, you must maintain a minimum balance of [cycles](terminology.md#cycles). @@ -42,9 +42,9 @@ You can top up your cycle balance in the Juno [console](https://console.juno.bui ## Transaction costs -New developers who join Juno are granted credits to create a mission control and their initial [satellite]. +New developers who join Juno are granted credits to create a Mission Control and their initial [satellite]. -To create additional satellites, a fee of 0.4 ICP is necessary, along with the infrastructure costs for setting up the container. +To create additional Satellites, a fee of 0.4 ICP is necessary, along with the infrastructure costs for setting up the container. Similarly, enabling analytics by creating an [orbiter] entails a fee of 0.4 ICP. @@ -78,7 +78,7 @@ To calculate the estimated monthly cost for 1 gigabyte of storage, you can refer Based on our experimentation, deploying an entire website, such as the website http://juno.build, which consists of approximately 900 files (including compressed versions of the files) and is 40 MB in size, is estimated to cost around 0.114 T Cycles, which converts to 0.0105 ICP ($0.15). -It's important to note that subsequent deployments of your project can have significantly lower costs if the build consistency of your application is maintained. Juno only uploads new files to your satellites, which helps reduce costs compared to initial deployments. +It's important to note that subsequent deployments of your project can have significantly lower costs if the build consistency of your application is maintained. Juno only uploads new files to your Satellites, which helps reduce costs compared to initial deployments. ### Data diff --git a/docs/reference/cli.mdx b/docs/reference/cli.mdx index ee992256..c9c12fa0 100644 --- a/docs/reference/cli.mdx +++ b/docs/reference/cli.mdx @@ -59,7 +59,7 @@ The authentication process requires a browser. If you've previously authenticated your terminal and decide to log in again, the CLI will prompt you about reusing your existing access key. -This allows you to reuse your authorization, especially when creating new modules like satellites or orbiters. +This allows you to reuse your authorization, especially when creating new modules like Satellites or Orbiters. --- @@ -67,7 +67,7 @@ This allows you to reuse your authorization, especially when creating new module :::caution -This action currently does not remove the controllers from satellites and/or mission control and/or orbiter. It only logs out your local machine by removing the locally saved key (principal). +This action currently does not remove the controllers from Satellites and/or Mission Control and/or Orbiter. It only logs out your local machine by removing the locally saved key (principal). ::: @@ -93,7 +93,7 @@ import HostingClear from "./cli/hosting-clear.md"; :::note -This command removes existing files from the satellite and only affects the app assets, your frontend. Your user's uploaded files will not be cleared from your custom collections in the storage. +This command removes existing files from the Satellite and only affects the app assets, your frontend. Your user's uploaded files will not be cleared from your custom collections in the storage. ::: diff --git a/docs/reference/configuration.mdx b/docs/reference/configuration.mdx index 73d146c5..e70c54e9 100644 --- a/docs/reference/configuration.mdx +++ b/docs/reference/configuration.mdx @@ -314,7 +314,7 @@ Orbiters are an optional component of your application used for analytics. ### ID -An orbiter has a unique identifier (id). This ID is used to reference the orbiter during operations and deployments. +An Orbiter has a unique identifier (id). This ID is used to reference the Orbiter during operations and deployments. diff --git a/docs/setup-the-sdk.mdx b/docs/setup-the-sdk.mdx index a3c39eef..e50810b9 100644 --- a/docs/setup-the-sdk.mdx +++ b/docs/setup-the-sdk.mdx @@ -47,7 +47,7 @@ import Core from "./components/core.mdx"; -2. Initialize your satellite in your web app: +2. Initialize your Satellite in your web app: ```typescript import { initSatellite } from "@junobuild/core"; diff --git a/docs/terminology.md b/docs/terminology.md index 9f0f1430..5f89394a 100644 --- a/docs/terminology.md +++ b/docs/terminology.md @@ -61,9 +61,9 @@ It is free and passwordless. It integrates WebAuthn for maximum compatibility an Mission control is the command center for your project. It is under your exclusive control, allowing it, for example, to hold ICP and perform various operations such as topping up your modules. -Think of it like the command center for a space mission. Just as NASA's mission control coordinates spacecraft and satellites, your mission control manages all your [satellites] or [orbiters](#orbiter). +Think of it like the command center for a space mission. Just as NASA's Mission Control coordinates spacecraft and Satellites, your Mission Control manages all your [satellites] or [orbiters](#orbiter). -Because it can hold ICP and is only controlled by you, your mission control also functions as your [wallet](#wallet). +Because it can hold ICP and is only controlled by you, your Mission Control also functions as your [wallet](#wallet). For a schematic representation, refer to the [Architecture](miscellaneous/architecture.md) documentation page. @@ -77,7 +77,7 @@ It acts as a comprehensive entity, encompassing memory, permission checks, and o ## Orbiter -An orbiter is an optional module you can enable for analytics. It helps you gather valuable, anonymous insights about your users. +An Orbiter is an optional module you can enable for analytics. It helps you gather valuable, anonymous insights about your users. ## Principal @@ -89,9 +89,9 @@ Learn more about [principals](https://internetcomputer.org/docs/current/referenc ## Satellite -A satellite is a container for your application. It holds your project’s data, storage, application bundle, and assets. +A Satellite is a container for your application. It holds your project’s data, storage, application bundle, and assets. -Each satellite is commonly dedicated to a single application. +Each Satellite is commonly dedicated to a single application. ## Subnet diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 20afedaf..1a6a8efe 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -67,7 +67,7 @@ To resolve this issue, make sure your SDK is correctly configured by following t ### Invalid character: "<" -When you scaffold an app with a template, the `juno.config` file includes placeholder values for the satellite IDs: +When you scaffold an app with a template, the `juno.config` file includes placeholder values for the Satellite IDs: ```typescript import { defineConfig } from "@junobuild/config"; @@ -87,7 +87,7 @@ If you start your frontend development server without replacing these placeholde This happens because the app tries to parse the config at runtime and encounters the invalid placeholder character `<` in the ID values. -Continue with your setup or tutorial until you receive your actual satellite ID(s). Once you’ve updated the config with real values, make sure to restart your development server. +Continue with your setup or tutorial until you receive your actual Satellite ID(s). Once you’ve updated the config with real values, make sure to restart your development server. :::note From 14478ede2b57430ed9c7cf46bd3b004a1fa7f904 Mon Sep 17 00:00:00 2001 From: github-actions <41898282+github-actions[bot]@users.noreply.github.com> Date: Wed, 7 Jan 2026 08:39:50 +0000 Subject: [PATCH 2/2] =?UTF-8?q?=F0=9F=93=84=20Update=20LLMs.txt=20snapshot?= =?UTF-8?q?=20for=20PR=20review?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .llms-snapshots/llms-full.txt | 100 +++++++++++++++++----------------- .llms-snapshots/llms.txt | 10 ++-- 2 files changed, 55 insertions(+), 55 deletions(-) diff --git a/.llms-snapshots/llms-full.txt b/.llms-snapshots/llms-full.txt index a9b38cae..aa02f24a 100644 --- a/.llms-snapshots/llms-full.txt +++ b/.llms-snapshots/llms-full.txt @@ -185,7 +185,7 @@ yarn add @junobuild/core @icp-sdk/core @icp-sdk/auth @dfinity/utils pnpm add @junobuild/core @icp-sdk/core @icp-sdk/auth @dfinity/utils ``` -2. Initialize your satellite in your web app: +2. Initialize your Satellite in your web app: ``` import { initSatellite } from "@junobuild/core";await initSatellite(); @@ -470,10 +470,10 @@ For example, you can use the following script: When you're ready to deploy your project to production, you'll need to create a [satellite](/docs/terminology.md#satellite). 1. To get started, sign-in to the Juno [console](https://console.juno.build). If you are a new developer on Juno and the Internet Computer, you may be prompted to create your first anonymous [Internet Identity](/docs/terminology.md#internet-identity). -2. Click **Launch a new satellite**. -3. Enter a name for your satellite (note: this is for display purposes only and does not need to be unique). +2. Click **Launch a new Satellite**. +3. Enter a name for your Satellite (note: this is for display purposes only and does not need to be unique). 4. Confirm with **Create a Satellite.** -5. The platform will then create your satellite and provision its resources. +5. The platform will then create your Satellite and provision its resources. 6. Once the process is complete, click **Continue** to access the overview page. 🎉 You’re all set! You can now deploy your frontend app, static website, or publish your serverless functions to production. @@ -973,7 +973,7 @@ If you prefer to control this part as well, or if you want to improve redundancy [Internet Identity](https://identity.ic0.app) lets users authenticate securely and anonymously through a decentralized identity system built for the Internet Computer. -When a user signs in with Internet Identity, they confirm their identity through the provider. If successful, a session is created automatically and the user can interact with your satellite. +When a user signs in with Internet Identity, they confirm their identity through the provider. If successful, a session is created automatically and the user can interact with your Satellite. Authentication with Internet Identity offers strong privacy guarantees and complete isolation between domains by design. @@ -1008,7 +1008,7 @@ Internet Identity sign-in can be customized with options that let you control se | --- | --- | --- | --- | | `maxTimeToLiveInNanoseconds` | `BigInt(4 * 60 * 60 * 1000 * 1000 * 1000)` | **4 hours** | Maximum lifetime of the user's session in **nanoseconds**. Once expired, the session cannot be extended. | | `windowed` | `boolean` | `true` | By default, the authentication flow is presented in a popup window on desktop that is automatically centered on the browser. This behavior can be turned off by setting the option to `false`, causing the authentication flow to happen in a separate tab instead. | -| `derivationOrigin` | `string` or `URL` | | The main domain to be used to ensure your users are identified with the same public ID, regardless of which of your satellite's URLs they use to access your application. | +| `derivationOrigin` | `string` or `URL` | | The main domain to be used to ensure your users are identified with the same public ID, regardless of which of your Satellite's URLs they use to access your application. | | `onProgress` | `(progress) => void` | | Callback for provider sign-in and user creation/loading. | | `domain` | `internetcomputer.org` or `ic0.app` or `id.ai` | `internetcomputer.org` | The domain on which to open Internet Identity. | @@ -1062,7 +1062,7 @@ If you're unsure which domain to use as the primary domain, here are two common * You're still experimenting with your domain setup and might change it later. * You're not ready to commit to a long-term domain. - * You plan to host multiple satellites under different domains and don't want to tie user identity to just one. + * You plan to host multiple Satellites under different domains and don't want to tie user identity to just one. Choosing the right derivation origin early helps avoid identity issues later, but both approaches are valid depending on your goals. @@ -1413,9 +1413,9 @@ Permissions define who can read and write documents in a collection. Writing inc | Permission | Description | | --- | --- | | **Public** | Anyone can read or write documents in the collection. | -| **Private** | Only the creator (owner) of a document can read or write to it. However, note that since satellite administrators manage the underlying infrastructure, they have the technical ability to modify access rules by changing its source code. | -| **Managed** | The owner of a document, the administrator and editor of the satellite can read or write to it in the collection. | -| **Restricted** | Only satellite administrator and editor can read or write any document in the collection. | +| **Private** | Only the creator (owner) of a document can read or write to it. However, note that since Satellite administrators manage the underlying infrastructure, they have the technical ability to modify access rules by changing its source code. | +| **Managed** | The owner of a document, the administrator and editor of the Satellite can read or write to it in the collection. | +| **Restricted** | Only Satellite administrator and editor can read or write any document in the collection. | If not set to immutable, you can modify the permissions at any time, and the changes will take effect immediately. @@ -1493,7 +1493,7 @@ To update a document, use the `setDoc` function with its current version to vali import { setDoc } from "@junobuild/core";await setDoc({ collection: "my_collection_key", doc: { key: myId, data: myExample, version: 3n }}); ``` -The `version` must match the current version of the last document within the satellite; otherwise, the call will fail. This prevents unexpected concurrent overwrites, which is useful, for example, if your users use your projects simultaneously on multiple devices. +The `version` must match the current version of the last document within the Satellite; otherwise, the call will fail. This prevents unexpected concurrent overwrites, which is useful, for example, if your users use your projects simultaneously on multiple devices. **Tip:** @@ -1649,7 +1649,7 @@ To delete a document, use the `deleteDoc` function, which performs version valid import { deleteDoc } from "@junobuild/core";await deleteDoc({ collection: "my_collection_key", doc: myDoc}); ``` -The document must include the current `version` from the latest entry within the satellite; otherwise, the call will fail. This prevents unexpected concurrent overwrites, which is particularly useful if your users access your projects simultaneously on multiple devices. +The document must include the current `version` from the latest entry within the Satellite; otherwise, the call will fail. This prevents unexpected concurrent overwrites, which is particularly useful if your users access your projects simultaneously on multiple devices. ### Delete multiple documents @@ -2092,7 +2092,7 @@ The list below outlines the available hosting options you can configure to tailo ### Source -The `source` field specifies the directory that contains the built assets for your satellite. This is typically the output directory generated by your build process after running a command like `npm run build`. +The `source` field specifies the directory that contains the built assets for your Satellite. This is typically the output directory generated by your build process after running a command like `npm run build`. Commonly, or if you are using the templates, these are the folders that can be set as the `source` field: @@ -2103,7 +2103,7 @@ Commonly, or if you are using the templates, these are the folders that can be s | SvelteKit | `build` | | Angular | `dist//browser` | -Juno uses this directory to locate the files that will be deployed as part of your satellite. Ensure that this directory includes all the necessary assets, such as HTML, JavaScript, CSS, and any other static or dynamic resources your application requires. +Juno uses this directory to locate the files that will be deployed as part of your Satellite. Ensure that this directory includes all the necessary assets, such as HTML, JavaScript, CSS, and any other static or dynamic resources your application requires. juno.config.js @@ -2113,7 +2113,7 @@ import { defineConfig } from "@junobuild/config";export default defineConfig({ ### Ignore files -The `ignore` attribute allows you to exclude certain files from being deployed to your satellite. +The `ignore` attribute allows you to exclude certain files from being deployed to your Satellite. This attribute works similarly to Git's `.gitignore`, and you can specify which files to ignore using globs. @@ -2127,7 +2127,7 @@ import { defineConfig } from "@junobuild/config";export default defineConfig({ ### HTTP Headers -Headers allow the client and the satellite to pass additional information along with a request or a response. Some sets of headers can affect how the browser handles the page and its content. +Headers allow the client and the Satellite to pass additional information along with a request or a response. Some sets of headers can affect how the browser handles the page and its content. For instance, you may want to set a specific `Cache-Control` for performance reasons. @@ -2153,7 +2153,7 @@ The `headers` is an array of objects, each containing `key` and `value`, and the By default, all unknown paths are automatically rewritten to `/index.html`. However, if you wish to serve a custom `404 Not Found` error when a user attempts to access a non-existent page, you can do so without requiring additional configuration. -Simply upload a custom `404.html` file to your satellite that should be served from the root path of your site. +Simply upload a custom `404.html` file to your Satellite that should be served from the root path of your site. ### Redirects @@ -2275,7 +2275,7 @@ import { defineConfig } from "@junobuild/config";export default defineConfig({ ### Encoding types -When deploying, the CLI automatically maps the encoding type based on the file extension. The encoding information is then used in the satellite to provide the appropriate HTTP response header `Content-Encoding`. +When deploying, the CLI automatically maps the encoding type based on the file extension. The encoding information is then used in the Satellite to provide the appropriate HTTP response header `Content-Encoding`. The default mappings are as follows: @@ -2340,7 +2340,7 @@ This section covers how to configure and manage your custom domain in Juno, incl To connect your custom domain, follow these steps: 1. Start the custom domain wizard from the Juno console [hosting](https://console.juno.build/hosting) page -2. Enter the desired domain name for your satellite +2. Enter the desired domain name for your Satellite 3. Log into your domain provider's site and configure the DNS records as indicated by Juno 4. Continue the process in Juno @@ -2441,9 +2441,9 @@ Assets are publicly accessible on the Internet regardless of the permission sche | Permission | Description | | --- | --- | | **Public** | Anyone can read or write assets in the collection. | -| **Private** | Only the creator (owner) of the asset can read or write to it. However, note that since satellite administrators manage the underlying infrastructure, they have the technical ability to modify access rules by changing its source code. | -| **Managed** | The owner of an asset, the administrator and editor of the satellite can read or write to it in the collection. | -| **Restricted** | Only satellite administrator and editor can read or write any asset in the collection. | +| **Private** | Only the creator (owner) of the asset can read or write to it. However, note that since Satellite administrators manage the underlying infrastructure, they have the technical ability to modify access rules by changing its source code. | +| **Managed** | The owner of an asset, the administrator and editor of the Satellite can read or write to it in the collection. | +| **Restricted** | Only Satellite administrator and editor can read or write any asset in the collection. | If not set to immutable, you can modify the permissions at any time, and the changes will take effect immediately. @@ -5567,7 +5567,7 @@ Learn how to integrate Juno with Angular. Follow our quickstart guide to set up [## 📄️ Deploy -Learn how to deploy your Angular project to Juno. Follow the deployment guide to configure static exports, set up your satellite, and publish your site to production.](/docs/guides/angular/deploy.md) +Learn how to deploy your Angular project to Juno. Follow the deployment guide to configure static exports, set up your Satellite, and publish your site to production.](/docs/guides/angular/deploy.md) # Astro @@ -5579,7 +5579,7 @@ Learn how to integrate Juno with Astro. Follow our quickstart guide to set up yo [## 📄️ Deploy -Learn how to deploy your Astro project to Juno. Follow the deployment guide to configure static exports, set up your satellite, and publish your site to production.](/docs/guides/astro/deploy.md) +Learn how to deploy your Astro project to Juno. Follow the deployment guide to configure static exports, set up your Satellite, and publish your site to production.](/docs/guides/astro/deploy.md) # Docusaurus @@ -5587,7 +5587,7 @@ Explore how to deploy a Juno project developed with Docusaurus. [## 📄️ Deploy -Learn how to deploy your Docusaurus project to Juno. Follow the deployment guide to configure static exports, set up your satellite, and publish your site to production.](/docs/guides/docusaurus/deploy.md) +Learn how to deploy your Docusaurus project to Juno. Follow the deployment guide to configure static exports, set up your Satellite, and publish your site to production.](/docs/guides/docusaurus/deploy.md) # End-to-End Testing @@ -5859,7 +5859,7 @@ Learn how to integrate Juno with React. Follow our quickstart guide to set up yo [## 📄️ Deploy -Learn how to deploy your React project to Juno. Follow the deployment guide to configure static exports, set up your satellite, and publish your site to production.](/docs/guides/react/deploy.md) +Learn how to deploy your React project to Juno. Follow the deployment guide to configure static exports, set up your Satellite, and publish your site to production.](/docs/guides/react/deploy.md) # Code Functions in Rust @@ -6867,7 +6867,7 @@ Below are key considerations to ensure efficient and cost-effective deployment o ### Build Reproducibility -Only new resources will be deployed to your satellite. Changes are detected through sha256 comparison. Therefore, ensuring the build reproducibility of your application is crucial to accurately identify and deploy the necessary updates. +Only new resources will be deployed to your Satellite. Changes are detected through sha256 comparison. Therefore, ensuring the build reproducibility of your application is crucial to accurately identify and deploy the necessary updates. ### Deployment Costs @@ -8243,7 +8243,7 @@ When you sign in to Juno's [Console](/docs/terminology.md#console) using [Intern ![Juno's console flow](/assets/images/console-d0903e4989f7c4db5f4e85567211d266.png) -When you create a [satellite](/docs/terminology.md#satellite), you and your mission control become its owners. Per extension, you — and no one else (including not Juno) — own your satellite. +When you create a [satellite](/docs/terminology.md#satellite), you and your Mission Control become its owners. Per extension, you — and no one else (including not Juno) — own your satellite. **Note:** @@ -8262,7 +8262,7 @@ Each access key is assigned a **role** that defines what it can do: | **Write** | Editor | ✅ | ✅ | ✅ | ❌ | | **Submit** | Submitter | ✅ | ❌ | ❌ | ❌ | -An **administrator** can perform tasks such as configuring or deploying an app, topping up a mission control or satellite, creating a new collection in the [datastore](/docs/build/datastore.md) or [storage](/docs/build/storage.md), or configuring a custom domain in the [hosting](/docs/build/hosting.md). +An **administrator** can perform tasks such as configuring or deploying an app, topping up a Mission Control or satellite, creating a new collection in the [datastore](/docs/build/datastore.md) or [storage](/docs/build/storage.md), or configuring a custom domain in the [hosting](/docs/build/hosting.md). An **editor** can publish new serverless function versions to a Satellite’s CDN, deploy your frontend application, and read data from a collection. However, it cannot directly upgrade a Satellite or start/stop a module. @@ -8706,7 +8706,7 @@ For most applications, we recommend using the default subnets and staying on the | Subnet ID | Type | Canisters (Running/Stopped) | Nodes (Up/Total) | | --- | --- | --- | --- | -| 6pbhf-qzpdk-kuqbr-pklfa-5ehhf-jfjps-zsj6q-57nrl-kzhpd-mu7hc-vae | Juno's Subnet | 35885/697 | 13/13 | +| 6pbhf-qzpdk-kuqbr-pklfa-5ehhf-jfjps-zsj6q-57nrl-kzhpd-mu7hc-vae | Juno's Subnet | 36001/696 | 13/13 | | pzp6e-ekpqk-3c5x7-2h6so-njoeq-mt45d-h3h6c-q3mxf-vpeq5-fk5o7-yae | Fiduciary | 3564/12 | 34/34 | | bkfrj-6k62g-dycql-7h53p-atvkj-zg4to-gaogh-netha-ptybj-ntsgw-rqe | European | 25096/663 | 13/13 | | brlsh-zidhj-3yy3e-6vqbz-7xnih-xeq2l-as5oc-g32c4-i5pdn-2wwof-oae | | 35432/815 | 13/13 | @@ -8976,7 +8976,7 @@ The authentication process requires a browser. If you've previously authenticated your terminal and decide to log in again, the CLI will prompt you about reusing your existing access key. -This allows you to reuse your authorization, especially when creating new modules like satellites or orbiters. +This allows you to reuse your authorization, especially when creating new modules like Satellites or Orbiters. --- @@ -8984,7 +8984,7 @@ This allows you to reuse your authorization, especially when creating new module **Caution:** -This action currently does not remove the controllers from satellites and/or mission control and/or orbiter. It only logs out your local machine by removing the locally saved key (principal). +This action currently does not remove the controllers from Satellites and/or Mission Control and/or Orbiter. It only logs out your local machine by removing the locally saved key (principal). Log out of the current device. ⚠️ This action does not remove the access keys from the module. @@ -9014,7 +9014,7 @@ Usage: juno hosting clear [options]Options: -f, --fullPath Clear a parti **Note:** -This command removes existing files from the satellite and only affects the app assets, your frontend. Your user's uploaded files will not be cleared from your custom collections in the storage. +This command removes existing files from the Satellite and only affects the app assets, your frontend. Your user's uploaded files will not be cleared from your custom collections in the storage. --- @@ -9396,7 +9396,7 @@ If you are using a framework like Next.js or Vite, Juno provides plugins to simp ### Source -The `source` field specifies the directory that contains the built assets for your satellite. This is typically the output directory generated by your build process after running a command like `npm run build`. +The `source` field specifies the directory that contains the built assets for your Satellite. This is typically the output directory generated by your build process after running a command like `npm run build`. Commonly, or if you are using the templates, these are the folders that can be set as the `source` field: @@ -9407,7 +9407,7 @@ Commonly, or if you are using the templates, these are the folders that can be s | SvelteKit | `build` | | Angular | `dist//browser` | -Juno uses this directory to locate the files that will be deployed as part of your satellite. Ensure that this directory includes all the necessary assets, such as HTML, JavaScript, CSS, and any other static or dynamic resources your application requires. +Juno uses this directory to locate the files that will be deployed as part of your Satellite. Ensure that this directory includes all the necessary assets, such as HTML, JavaScript, CSS, and any other static or dynamic resources your application requires. juno.config.js @@ -9417,7 +9417,7 @@ import { defineConfig } from "@junobuild/config";export default defineConfig({ ### Ignore files -The `ignore` attribute allows you to exclude certain files from being deployed to your satellite. +The `ignore` attribute allows you to exclude certain files from being deployed to your Satellite. This attribute works similarly to Git's `.gitignore`, and you can specify which files to ignore using globs. @@ -9510,7 +9510,7 @@ import { defineConfig } from "@junobuild/config";export default defineConfig({ ### Encoding -When deploying, the CLI automatically maps the encoding type based on the file extension. The encoding information is then used in the satellite to provide the appropriate HTTP response header `Content-Encoding`. +When deploying, the CLI automatically maps the encoding type based on the file extension. The encoding information is then used in the Satellite to provide the appropriate HTTP response header `Content-Encoding`. The default mappings are as follows: @@ -9566,7 +9566,7 @@ The `storage` configuration accepts the following options and parameters: #### HTTP Headers -Headers allow the client and the satellite to pass additional information along with a request or a response. Some sets of headers can affect how the browser handles the page and its content. +Headers allow the client and the Satellite to pass additional information along with a request or a response. Some sets of headers can affect how the browser handles the page and its content. For instance, you may want to set a specific `Cache-Control` for performance reasons. @@ -9734,7 +9734,7 @@ Orbiters are an optional component of your application used for analytics. ### ID -An orbiter has a unique identifier (id). This ID is used to reference the orbiter during operations and deployments. +An Orbiter has a unique identifier (id). This ID is used to reference the Orbiter during operations and deployments. **Tip:** @@ -11892,7 +11892,7 @@ From there, you can dive into the details below to estimate storage, deployment, ## Operating costs -As the owner of your mission control, satellites and orbiters, you are responsible for their operating costs. +As the owner of your Mission Control, Satellites and Orbiters, you are responsible for their operating costs. To ensure that your infrastructure usage is covered, you must maintain a minimum balance of [cycles](/docs/terminology.md#cycles). @@ -11906,9 +11906,9 @@ You can top up your cycle balance in the Juno [console](https://console.juno.bui ## Transaction costs -New developers who join Juno are granted credits to create a mission control and their initial [satellite](/docs/terminology.md#satellite). +New developers who join Juno are granted credits to create a Mission Control and their initial [satellite](/docs/terminology.md#satellite). -To create additional satellites, a fee of 0.4 ICP is necessary, along with the infrastructure costs for setting up the container. +To create additional Satellites, a fee of 0.4 ICP is necessary, along with the infrastructure costs for setting up the container. Similarly, enabling analytics by creating an [orbiter](/docs/terminology.md#orbiter) entails a fee of 0.4 ICP. @@ -11940,7 +11940,7 @@ To calculate the estimated monthly cost for 1 gigabyte of storage, you can refer Based on our experimentation, deploying an entire website, such as the website [http://juno.build](http://juno.build), which consists of approximately 900 files (including compressed versions of the files) and is 40 MB in size, is estimated to cost around 0.114 T Cycles, which converts to 0.0105 ICP ($0.15). -It's important to note that subsequent deployments of your project can have significantly lower costs if the build consistency of your application is maintained. Juno only uploads new files to your satellites, which helps reduce costs compared to initial deployments. +It's important to note that subsequent deployments of your project can have significantly lower costs if the build consistency of your application is maintained. Juno only uploads new files to your Satellites, which helps reduce costs compared to initial deployments. ### Data @@ -12017,9 +12017,9 @@ It is free and passwordless. It integrates WebAuthn for maximum compatibility an Mission control is the command center for your project. It is under your exclusive control, allowing it, for example, to hold ICP and perform various operations such as topping up your modules. -Think of it like the command center for a space mission. Just as NASA's mission control coordinates spacecraft and satellites, your mission control manages all your [satellites](/docs/terminology.md#satellite) or ([orbiters](#orbiter)). +Think of it like the command center for a space mission. Just as NASA's Mission Control coordinates spacecraft and Satellites, your Mission Control manages all your [satellites](/docs/terminology.md#satellite) or ([orbiters](#orbiter)). -Because it can hold ICP and is only controlled by you, your mission control also functions as your ([wallet](#wallet)). +Because it can hold ICP and is only controlled by you, your Mission Control also functions as your ([wallet](#wallet)). For a schematic representation, refer to the [Architecture](/docs/miscellaneous/architecture.md) documentation page. @@ -12033,7 +12033,7 @@ It acts as a comprehensive entity, encompassing memory, permission checks, and o ## Orbiter -An orbiter is an optional module you can enable for analytics. It helps you gather valuable, anonymous insights about your users. +An Orbiter is an optional module you can enable for analytics. It helps you gather valuable, anonymous insights about your users. ## Principal @@ -12045,9 +12045,9 @@ Learn more about [principals](https://internetcomputer.org/docs/current/referenc ## Satellite -A satellite is a container for your application. It holds your project’s data, storage, application bundle, and assets. +A Satellite is a container for your application. It holds your project’s data, storage, application bundle, and assets. -Each satellite is commonly dedicated to a single application. +Each Satellite is commonly dedicated to a single application. ## Subnet @@ -12135,7 +12135,7 @@ To resolve this issue, make sure your SDK is correctly configured by following t ### Invalid character: "<" -When you scaffold an app with a template, the `juno.config` file includes placeholder values for the satellite IDs: +When you scaffold an app with a template, the `juno.config` file includes placeholder values for the Satellite IDs: ``` import { defineConfig } from "@junobuild/config";export default defineConfig({ satellite: { ids: { development: "", production: "" }, source: "dist" }}); @@ -12145,7 +12145,7 @@ If you start your frontend development server without replacing these placeholde This happens because the app tries to parse the config at runtime and encounters the invalid placeholder character `<` in the ID values. -Continue with your setup or tutorial until you receive your actual satellite ID(s). Once you’ve updated the config with real values, make sure to restart your development server. +Continue with your setup or tutorial until you receive your actual Satellite ID(s). Once you’ve updated the config with real values, make sure to restart your development server. **Note:** diff --git a/.llms-snapshots/llms.txt b/.llms-snapshots/llms.txt index 57a46a79..f3e574bb 100644 --- a/.llms-snapshots/llms.txt +++ b/.llms-snapshots/llms.txt @@ -91,7 +91,7 @@ Juno is your self-contained serverless platform for building full-stack web apps ## Guides -- [AI](https://juno.build/docs/guides/ai.md): Learn how to use Juno's llms.txt files to provide AI tools with better context for building serverless functions, deploying satellites, and integrating the SDK. +- [AI](https://juno.build/docs/guides/ai.md): Learn how to use Juno's llms.txt files to provide AI tools with better context for building serverless functions, deploying Satellites, and integrating the SDK. - [Angular](https://juno.build/docs/guides/angular.md): Explore how to create a Juno project developed with Angular. - [Astro](https://juno.build/docs/guides/astro.md): Explore how to create a Juno project developed with Astro. - [Docusaurus](https://juno.build/docs/guides/docusaurus.md): Explore how to deploy a Juno project developed with Docusaurus. @@ -108,16 +108,16 @@ Juno is your self-contained serverless platform for building full-stack web apps ## Guides - Angular - [Build an Angular App](https://juno.build/docs/guides/angular/build.md): Learn how to integrate Juno with Angular. Follow our quickstart guide to set up your development environment, configure your project, and start building with Juno. -- [Deploy an Angular App](https://juno.build/docs/guides/angular/deploy.md): Learn how to deploy your Angular project to Juno. Follow the deployment guide to configure static exports, set up your satellite, and publish your site to production. +- [Deploy an Angular App](https://juno.build/docs/guides/angular/deploy.md): Learn how to deploy your Angular project to Juno. Follow the deployment guide to configure static exports, set up your Satellite, and publish your site to production. ## Guides - Astro - [Build an Astro App](https://juno.build/docs/guides/astro/build.md): Learn how to integrate Juno with Astro. Follow our quickstart guide to set up your development environment, configure your project, and start building with Juno. -- [Deploy an Astro Site](https://juno.build/docs/guides/astro/deploy.md): Learn how to deploy your Astro project to Juno. Follow the deployment guide to configure static exports, set up your satellite, and publish your site to production. +- [Deploy an Astro Site](https://juno.build/docs/guides/astro/deploy.md): Learn how to deploy your Astro project to Juno. Follow the deployment guide to configure static exports, set up your Satellite, and publish your site to production. ## Guides - Docusaurus -- [Deploy a Docusaurus Site](https://juno.build/docs/guides/docusaurus/deploy.md): Learn how to deploy your Docusaurus project to Juno. Follow the deployment guide to configure static exports, set up your satellite, and publish your site to production. +- [Deploy a Docusaurus Site](https://juno.build/docs/guides/docusaurus/deploy.md): Learn how to deploy your Docusaurus project to Juno. Follow the deployment guide to configure static exports, set up your Satellite, and publish your site to production. ## Guides - Github-actions @@ -133,7 +133,7 @@ Juno is your self-contained serverless platform for building full-stack web apps ## Guides - React - [Build a React App](https://juno.build/docs/guides/react/build.md): Learn how to integrate Juno with React. Follow our quickstart guide to set up your development environment, configure your project, and start building with Juno. -- [Deploy a React App](https://juno.build/docs/guides/react/deploy.md): Learn how to deploy your React project to Juno. Follow the deployment guide to configure static exports, set up your satellite, and publish your site to production. +- [Deploy a React App](https://juno.build/docs/guides/react/deploy.md): Learn how to deploy your React project to Juno. Follow the deployment guide to configure static exports, set up your Satellite, and publish your site to production. ## Guides - Sveltekit