Skip to content

Commit f2a17f7

Browse files
committed
revision
1 parent c010511 commit f2a17f7

File tree

14 files changed

+61
-55
lines changed

14 files changed

+61
-55
lines changed

docs/bee/installation/package-manager.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -440,8 +440,8 @@ curl -s localhost:1633/peers | jq ".peers | length"
440440
Perfect! We are accumulating peers, this means you are connected to
441441
the network, and ready to start [using
442442
Bee](/docs/develop/introduction) to [upload and
443-
download](/docs/develop/access-the-swarm/upload-and-download) content or host
444-
and browse [websites](/docs/develop/access-the-swarm/host-your-website) hosted
443+
download](/docs/develop/upload-and-download) content or host
444+
and browse [websites](/docs/develop/host-your-website) hosted
445445
on the Swarm network.
446446
447447
Welcome to the swarm! 🐝 🐝 🐝 🐝 🐝

docs/bee/working-with-bee/bee-api.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ Detailed information about Bee API endpoints can be found in the [API reference
1717

1818
## Interacting With the API
1919

20-
You can interact with the Bee API using standard HTTP requests, allowing you to programmatically access all of your Bee node's various functions such as [purchasing stamp batches](/docs/develop/tools-and-features/buy-a-stamp-batch), [uploading and downloading](/docs/develop/access-the-swarm/upload-and-download), [staking](/docs/bee/working-with-bee/staking), and more.
20+
You can interact with the Bee API using standard HTTP requests, allowing you to programmatically access all of your Bee node's various functions such as [purchasing stamp batches](/docs/develop/tools-and-features/buy-a-stamp-batch), [uploading and downloading](/docs/develop/upload-and-download), [staking](/docs/bee/working-with-bee/staking), and more.
2121

2222
### Alternatives for Working with the API
2323

docs/bee/working-with-bee/node-types.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,8 +18,8 @@ Bee can operate in different modes, each tailored to specific use cases:
1818

1919
| Feature | Full Node | Light Node | Ultra-Light Node |
2020
| ----------------------------------------------------------------------- | --------- | ---------- | ---------------- |
21-
| Free tier [downloads](/docs/develop/access-the-swarm/upload-and-download) ||||
22-
| [Uploading](/docs/develop/access-the-swarm/upload-and-download) (Can purchase [postage stamp batches](/docs/develop/tools-and-features/buy-a-stamp-batch)) ||||
21+
| Free tier [downloads](/docs/develop/upload-and-download) ||||
22+
| [Uploading](/docs/develop/upload-and-download) (Can purchase [postage stamp batches](/docs/develop/tools-and-features/buy-a-stamp-batch)) ||||
2323
| Can exceed free tier downloads ||||
2424
| Storage sharing ||||
2525
| [Storage incentives](/docs/bee/working-with-bee/staking/) ||||

docs/concepts/access-control.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ id: access-control
66
The Access Control Trie (ACT) implements the operation of encryption at the chunk level, with the presence of a decryption/encryption key being the only distinction between accessing private and public data.
77

88
:::info
9-
This article describes the high level concepts and functionalities of ACT. If you're ready to try it out for yourself, please refer to this [hands on usage guide with specific details](/docs/develop/access-the-swarm/act/).
9+
This article describes the high level concepts and functionalities of ACT. If you're ready to try it out for yourself, please refer to this [hands on usage guide with specific details](/docs/develop/act/).
1010
:::
1111

1212
In decentralized public data storage systems like Swarm, data is distributed across multiple nodes. Ensuring

docs/concepts/what-is-swarm.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ Built on top of the overlay network is also an [incentives layer](/docs/concepts
5656

5757
The third part of Swarm is a component that provides high-level data access and defines APIs for base-layer features. This layer is responsible for providing an easy-to-use interface for developers to interact with Swarm's underlying storage and communication infrastructure.
5858

59-
Swarm's high-level data access component provides [APIs that allow developers to perform various operations](/api/) on the network, including [uploading and downloading data](/docs/develop/access-the-swarm/upload-and-download) and searching for content. These APIs are designed to be simple and intuitive, making it easy for developers to build decentralised applications on top of Swarm.
59+
Swarm's high-level data access component provides [APIs that allow developers to perform various operations](/api/) on the network, including [uploading and downloading data](/docs/develop/upload-and-download) and searching for content. These APIs are designed to be simple and intuitive, making it easy for developers to build decentralised applications on top of Swarm.
6060

6161
### 4. Application Layer
6262

File renamed without changes.

docs/develop/access-the-swarm/introduction.md

Lines changed: 0 additions & 12 deletions
This file was deleted.

docs/develop/access-the-swarm/host-your-website.md renamed to docs/develop/host-your-website.md

Lines changed: 19 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -6,19 +6,21 @@ id: host-your-website
66
import Tabs from '@theme/Tabs';
77
import TabItem from '@theme/TabItem';
88

9-
# Hosting a Website on Swarm and Linking it to ENS
9+
This guide explains how to host a website on Swarm using `swarm-cli` and make it accessible through [Ethereum Name Service (ENS)](https://ens.domains/).
1010

11-
This guide explains how to host a static website on Bee using `swarm-cli` and make it accessible through [Ethereum Name Service (ENS)](https://ens.domains/).
11+
## Host a Site With **swarm-cli**
1212

13-
**Part one** covers uploading and accessing your site through the raw Swarm hash.
13+
This three part guide shows you how to get your website hosted on Swarm with just a few simple commands by using `swarm-cli` from your terminal.
14+
15+
**Part one** covers uploading and accessing your site through the raw Swarm hash.
1416

1517
**Part two** shows how to register your Swarm hash with your ENS domain so it can be easily accessed by anyone through public ENS gateways like `eth.limo`, `bzz.link`, or `localhost` on a Bee node.
1618

17-
**Part three** shows how to upload your website through a feed and register the feed manifest with ENS in order to provide a static hash for the website. This means you no longer need to update your ENS record every time you make a change to your website, and is the recommended method for hosting a publicly accessible website on Swarm.
19+
**Part three** shows you how to use feeds to make you website accessible at a static hash, and then use that hash to connect with your ENS domain. This is highly recommended for any site which will have future updates - without this step you would need to re-register your ENS domain every time you updated the site.
1820

19-
## 1. Hosting and Accessing Your Website on Swarm
21+
### 1. Upload & Access by Hash
2022

21-
### Prerequisites
23+
#### Prerequisites
2224

2325
* A running Bee node (either a [standard installation](/docs/bee/installation/quick-start) or [Swarm Desktop](/docs/desktop/install))
2426
* A valid postage batch
@@ -29,7 +31,7 @@ This guide explains how to host a static website on Bee using `swarm-cli` and ma
2931
You can download the example website files from the [ethersphere/examples](https://github.com/ethersphere/examples/tree/main/basic-static-website) repository.
3032

3133

32-
### Uploading the Website
34+
#### Uploading the Website
3335

3436
1. Go to the folder containing your website files.
3537

@@ -96,7 +98,7 @@ cf50756e6115445fd283691673fa4ad2204849558a6f3b3f4e632440f1c3ab7c
9698
Copy this and save it. You’ll need it for both direct access and ENS integration.
9799

98100

99-
### Accessing the Website
101+
#### Accessing the Website
100102

101103
Anyone with a Bee node can now access the site using the Swarm hash you just saved:
102104

@@ -105,7 +107,7 @@ http://localhost:1633/bzz/<swarm-hash>/
105107
```
106108

107109

108-
## 2. Connecting Your Website to ENS
110+
### 2. (Recommended) Connect Site to ENS Domain
109111

110112
Once the site is uploaded, you can make it accessible via an easy to remember ENS domain name:
111113

@@ -141,7 +143,7 @@ https://eth-mainnet.public.blastapi.io
141143
Alternatively, you can run your own Ethereum node and use that as the RPC.
142144
:::
143145

144-
### Using the Official ENS Guide
146+
#### Using the Official ENS Guide
145147

146148
The ENS team provides a clear walkthrough with screenshots showing how to add a content hash to your domain with their [easy to use app](https://app.ens.domains/):
147149

@@ -155,7 +157,7 @@ The guide covers:
155157
* Confirming the transaction
156158

157159

158-
### Swarm-Specific Step
160+
#### Swarm-Specific Step
159161

160162
When you reach Step 2 in the ENS guide (“Add content hash record”), enter your Swarm reference in the following format:
161163

@@ -178,7 +180,7 @@ This works across:
178180
You do not need to encode the hash or use any additional tools. `bzz://<hash>` is sufficient.
179181

180182

181-
## 3. (Recommended) Host Your Website via a Feed Instead of a Raw Hash
183+
### 3. (Recommended) Avoid Repeated ENS Registrations with Feeds
182184

183185
If you plan to update your website in the future, you should publish your website hash to a **feed** rather than pointing ENS directly to the raw content hash.
184186

@@ -197,7 +199,7 @@ In this section, you will:
197199

198200
This ensures future website updates require no ENS changes.
199201

200-
### Prerequisite: Have your initial site hash
202+
#### Prerequisite: Have your initial site hash
201203

202204
From Part One you should already have uploaded your site and seen something like:
203205

@@ -210,7 +212,7 @@ We will refer to this as `<site-hash>` in the examples below.
210212
> In the next step we will re-upload the site using a feed so that ENS can always track updates.
211213
212214

213-
### Step 1: Create a dedicated publisher identity
215+
#### Step 1: Create a dedicated publisher identity
214216

215217
This key will sign feed updates.
216218

@@ -227,7 +229,7 @@ swarm-cli identity export website-publisher
227229
```
228230

229231

230-
### Step 2: Upload your website to a feed (creates the manifest automatically)
232+
#### Step 2: Upload your website to a feed (creates the manifest automatically)
231233

232234
<Tabs>
233235
<TabItem value="linux" label="Linux / macOS">
@@ -275,7 +277,7 @@ Save this hash, you will use it for the next step.
275277
This is your **permanent website reference**. It is a reference to a feed manifest which points to the latest feed entry so that you can use it as a static, unchanging reference for your website even as you make multiple updates to the site. Every time you update the website through the feed, this manifest will point to the hash for the newest version of the website.
276278

277279

278-
### Step 3: Use the feed reference as the ENS contenthash
280+
#### Step 3: Use the feed reference as the ENS contenthash
279281

280282
Follow the same [official ENS guide](https://support.ens.domains/en/articles/12275979-how-to-add-a-decentralized-website-to-an-ens-name) for registering a content hash adding your content hash in the ENS UI (see [Section 2](#2-connecting-your-website-to-ens)). However, this time, rather than registering your website's hash directly, register the feed manifest hash we saved from the previous step (`6c30ef2254ac15658959cb18dd123bcce7c16d06fa7d0d4550a1ee87b0a846a2` from our example above).
281283

@@ -287,7 +289,7 @@ bzz://6c30ef2254ac15658959cb18dd123bcce7c16d06fa7d0d4550a1ee87b0a846a2
287289

288290
Now your ENS name will always point to a static reference which will always resolve to the latest version of your website.
289291

290-
### Updating your site in the future
292+
#### Updating your site in the future
291293

292294
When you have a new version of your site, just run `feed upload` again against the same topic and identity:
293295

docs/develop/introduction.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ pagination_next: null
4444
<div class="container">
4545
<ul class="hub-grid">
4646
<li class="hub-card">
47-
<a class="hub-card__link" href="/docs/develop/access-the-swarm/upload-and-download">
47+
<a class="hub-card__link" href="/docs/develop/upload-and-download">
4848
<h3 class="hub-card__title">Upload and Download</h3>
4949
<p class="hub-card__desc">
5050
Learn how to upload and download a variety of data types from Swarm (with support for both browser and Node.js environments).
@@ -53,7 +53,7 @@ pagination_next: null
5353
</a>
5454
</li>
5555
<li class="hub-card">
56-
<a class="hub-card__link" href="/docs/develop/access-the-swarm/host-your-website">
56+
<a class="hub-card__link" href="/docs/develop/host-your-website">
5757
<h3 class="hub-card__title">Host a Webpage</h3>
5858
<p class="hub-card__desc">
5959
Host a website on Swarm and link it to your ENS domain for easy access at through gateways and Bee nodes.
@@ -63,7 +63,7 @@ pagination_next: null
6363
</li>
6464
<!--
6565
<li class="hub-card">
66-
<a class="hub-card__link" href="/docs/develop/access-the-swarm/updatable-content">
66+
<a class="hub-card__link" href="/docs/develop/updatable-content">
6767
<h3 class="hub-card__title">Publish Updatable Content</h3>
6868
<p class="hub-card__desc">
6969
Learn how to host dynamic content on Swarm which can change over time such as a blog or personal website.
@@ -72,7 +72,7 @@ pagination_next: null
7272
</a>
7373
</li>
7474
<li class="hub-card">
75-
<a class="hub-card__link" href="/docs/develop/access-the-swarm/act">
75+
<a class="hub-card__link" href="/docs/develop/act">
7676
<h3 class="hub-card__title">Add Access Control</h3>
7777
<p class="hub-card__desc">
7878
Control who is able to view your uploaded content, such as a list of paid newsletter or blog subscribers.
@@ -81,7 +81,7 @@ pagination_next: null
8181
</a>
8282
</li>
8383
<li class="hub-card">
84-
<a class="hub-card__link" href="/docs/develop/access-the-swarm/messaging">
84+
<a class="hub-card__link" href="/docs/develop/messaging">
8585
<h3 class="hub-card__title">Messaging on Swarm</h3>
8686
<p class="hub-card__desc">
8787
Learn how to integrate Swarm-based messaging into your app — with support for both real-time messaging use cases and private encrypted messaging.

docs/develop/tools-and-features/erasure-coding.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ For more details of erasure coding costs, see [here](/docs/concepts/DISC/erasure
4545

4646
## Downloading Erasure Encoded Data
4747

48-
For a downloader, the process for downloading a file which has been erasure encoded does not require any changes from the [normal download process](/docs/develop/access-the-swarm/upload-and-download). There are several options for adjusting the default behaviour for erasure encoded downloads, however there is no need to adjust them.
48+
For a downloader, the process for downloading a file which has been erasure encoded does not require any changes from the [normal download process](/docs/develop/upload-and-download). There are several options for adjusting the default behaviour for erasure encoded downloads, however there is no need to adjust them.
4949

5050
### Default Download Behaviour
5151

@@ -87,7 +87,7 @@ An example download request may look something like this:
8787

8888
For this request, the redundancy strategy is set to 3 (RACE), which means that it will initiate a request for all data and parity chunks and continue to retrieve chunks until enough have been retrieved to reconstruct the source data. This is in contrast with the default strategy of DATA where only the data chunks will be retrieved.
8989

90-
However, as noted above, it is recommended to not adjust the default settings for these options, so a typical request would actually look like this (which is the exact same as a [normal download](/docs/develop/access-the-swarm/upload-and-download) without any additional options set):
90+
However, as noted above, it is recommended to not adjust the default settings for these options, so a typical request would actually look like this (which is the exact same as a [normal download](/docs/develop/upload-and-download) without any additional options set):
9191

9292

9393
```bash

0 commit comments

Comments
 (0)