Skip to content

Commit 4494b0a

Browse files
authored
Update docs on Siren port and other small updates (#8399)
Co-Authored-By: Tan Chee Keong <[email protected]>
1 parent e21a433 commit 4494b0a

File tree

3 files changed

+4
-4
lines changed

3 files changed

+4
-4
lines changed

book/src/advanced_blobs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ While both `--supernode` and `--semi-supernode` can serve blobs, a supernode wil
1717

1818
Combining `--prune-blobs false` and `--supernode` (or `--semi-supernode`) implies that no data columns will be pruned, and the node will be able to serve blobs since using the flag.
1919

20-
If you want historical blob data beyond the data availability period (18 days), you can backfill blobs or data columns with the experimental flag `--complete-blob-backfill`. However, do note that this is an experimental feature and it only works when the flag is present during a fresh checkpoint sync when the database is initialised. The flag will have no effect if the node is already running (with an existing database). During blob backfill, the feature may cause some issues, e.g., the node may block most of its peers.
20+
If you want historical blob data beyond the data availability period (18 days), you can backfill blobs or data columns with the experimental flag `--complete-blob-backfill`. However, do note that this is an experimental feature and it only works when the flag is present during a fresh checkpoint sync when the database is initialised. The flag will not backfill blobs if the node is already running (with an existing database). During blob backfill, the feature may cause some issues, e.g., the node may block most of its peers.
2121

2222
**⚠️ The following section on Blobs is archived and not maintained as blobs are stored in the form of data columns after the Fulu fork ⚠️**
2323

book/src/advanced_checkpoint_sync.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -160,7 +160,7 @@ curl -H "Accept: application/octet-stream" "http://localhost:5052/eth/v1/beacon/
160160

161161
where `$SLOT` is the slot number. A slot which is an epoch boundary slot (i.e., first slot of an epoch) should always be used for manual checkpoint sync.
162162

163-
If the block contains blobs, all state, block and blobs must be provided and must point to the same slot. The
163+
If the block contains blobs, all state, block and blobs must be provided and must point to the same slot (only applies for slots before Fulu). The
164164
state may be from the same slot as the block (unadvanced), or advanced to an epoch boundary,
165165
in which case it will be assumed to be finalized at that epoch.
166166

book/src/ui_installation.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -138,13 +138,13 @@ Navigate to the backend directory `cd backend`. Install all required Node packag
138138
139139
After initializing the backend, return to the root directory. Install all frontend dependencies by executing `yarn`. Build the frontend using `yarn build`. Start the frontend production server with `yarn start`.
140140
141-
This will allow you to access siren at `http://localhost:3000` by default.
141+
This will allow you to access siren at `http://localhost:3300` by default.
142142
143143
## Advanced configuration
144144
145145
### About self-signed SSL certificates
146146
147-
By default, internally, Siren is running on port 80 (plain, behind nginx), port 3000 (plain, direct) and port 443 (with SSL, behind nginx)). Siren will generate and use a self-signed certificate on startup. This will generate a security warning when you try to access the interface. We recommend to only disable SSL if you would access Siren over a local LAN or otherwise highly trusted or encrypted network (i.e. VPN).
147+
By default, internally, Siren is running on port 80 (plain, behind nginx), port 3300 (plain, direct) and port 443 (with SSL, behind nginx)). Siren will generate and use a self-signed certificate on startup. This will generate a security warning when you try to access the interface. We recommend to only disable SSL if you would access Siren over a local LAN or otherwise highly trusted or encrypted network (i.e. VPN).
148148
149149
#### Generating persistent SSL certificates and installing them to your system
150150

0 commit comments

Comments
 (0)