Deploy preview for PR 148 🛫

pr-preview/pr-148/blog/04_testnet_update.html

@@ -214,10 +214,10 @@ <h2 id="epochs"><a class="header" href="#epochs">Epochs</a></h2>
 <p>Walrus Testnet enables multiple epochs. Initially, the epoch duration is set to a single day to
 ensure the logic of epoch change is thoroughly tested. At Mainnet, epochs will likely be multiple
 weeks long.</p>
-<p>Now the expiry epoch of blobs is meaningful, and blobs will become unavailable after their expiry
-epoch. The store command may be used to extend the expiry epoch of a blob that is still available.
-This operation is efficient and only affects payments and metadata, and does not re-upload blob
-contents.</p>
+<p>The progress of epochs makes the expiry epoch of blobs meaningful, and blobs will become unavailable
+after their expiry epoch. The store command may be used to extend the expiry epoch of a blob that is
+still available. This operation is efficient and only affects payments and metadata, and does not
+re-upload blob contents.</p>
 <ul>
 <li>Find out the <a href="../usage/client-cli.html#walrus-system-information">current epoch</a> through the CLI.</li>
 <li>Find out how to store a blob for

pr-preview/pr-148/print.html

@@ -542,10 +542,10 @@ <h2 id="epochs"><a class="header" href="#epochs">Epochs</a></h2>
 <p>Walrus Testnet enables multiple epochs. Initially, the epoch duration is set to a single day to
 ensure the logic of epoch change is thoroughly tested. At Mainnet, epochs will likely be multiple
 weeks long.</p>
-<p>Now the expiry epoch of blobs is meaningful, and blobs will become unavailable after their expiry
-epoch. The store command may be used to extend the expiry epoch of a blob that is still available.
-This operation is efficient and only affects payments and metadata, and does not re-upload blob
-contents.</p>
+<p>The progress of epochs makes the expiry epoch of blobs meaningful, and blobs will become unavailable
+after their expiry epoch. The store command may be used to extend the expiry epoch of a blob that is
+still available. This operation is efficient and only affects payments and metadata, and does not
+re-upload blob contents.</p>
 <ul>
 <li>Find out the <a href="blog/../usage/client-cli.html#walrus-system-information">current epoch</a> through the CLI.</li>
 <li>Find out how to store a blob for
@@ -1188,7 +1188,7 @@ <h2 id="installation"><a class="header" href="#installation">Installation</a></h
 </div>
 </div>
 <p>You can download the latest build from our Google Cloud Storage (GCS) bucket (correctly setting the
-<code>$SYSTEM</code> variable)`:</p>
+<code>$SYSTEM</code> variable):</p>
 <pre><code class="language-sh">SYSTEM= # set this to your system: ubuntu-x86_64, ubuntu-x86_64-generic, macos-x86_64, macos-arm64, windows-x86_64.exe
 curl https://storage.googleapis.com/mysten-walrus-binaries/walrus-testnet-latest-$SYSTEM -o walrus
 chmod +x walrus
@@ -1669,7 +1669,7 @@ <h2 id="http-api-usage"><a class="header" href="#http-api-usage">HTTP API Usage<
 </div>
 <div>
 <p>Walrus aggregators and publishers expose their API specifications at the path <code>/v1/api</code>. You can
-view this in the browser` e.g., at <a href="https://aggregator.walrus-testnet.walrus.space/v1/api">https://aggregator.walrus-testnet.walrus.space/v1/api</a></p>
+view this in the browser, e.g., at <a href="https://aggregator.walrus-testnet.walrus.space/v1/api">https://aggregator.walrus-testnet.walrus.space/v1/api</a></p>
 </div>
 </div>
 <h3 id="store"><a class="header" href="#store">Store</a></h3>
@@ -2505,6 +2505,19 @@ <h2 id="update-the-site"><a class="header" href="#update-the-site">Update the si
 <p>The wallet you are using must be the <em>owner</em> of the Walrus Site object to be able to update it.</p>
 </div>
 </div>
+<div id="admonition-extending-the-expiration-date-of-an-existing-site" class="admonition admonish-danger" role="note" aria-labelledby="admonition-extending-the-expiration-date-of-an-existing-site-title">
+<div class="admonition-title">
+<div id="admonition-extending-the-expiration-date-of-an-existing-site-title">
+<p>Extending the expiration date of an existing site</p>
+</div>
+<a class="admonition-anchor-link" href="walrus-sites/tutorial-publish.html#admonition-extending-the-expiration-date-of-an-existing-site"></a>
+</div>
+<div>
+<p>To extend the expiration date of a previously-stored site, use the <code>update</code> command with the
+<code>--force</code> flag, and specify the number of additional epochs (from the current epoch) with the
+<code>--epochs</code> flag.</p>
+</div>
+</div>
 <div style="break-before: page; page-break-before: always;"></div><link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/[email protected]/dist/katex.min.css">
 <h1 id="bonus-set-a-suins-name"><a class="header" href="#bonus-set-a-suins-name">Bonus: Set a SuiNS name</a></h1>
 <p>Browsing a URL like <code>https://1lupgq2auevjruy7hs9z7tskqwjp5cc8c5ebhci4v57qyl4piy.walrus.site</code> is not
@@ -2661,9 +2674,9 @@ <h1 id="configuring-the-site-builder"><a class="header" href="#configuring-the-s
 through sensible defaults, so you should not need to touch them. Yet, for completeness, we provide
 here the details for all the configuration options.</p>
 <h2 id="minimal-configuration"><a class="header" href="#minimal-configuration">Minimal configuration</a></h2>
-<p>The config file is expected to be in <code>./builder.yaml</code>, and it is possible to point elsewhere with
-the <code>--config</code> flag. For your first run, it should be sufficient to call the <code>site-builder</code> with
-<code>--config site-builder/assets/builder-example.yaml</code>, which is already configured appropriately.</p>
+<p>The config file is expected to be in <code>./sites-config.yaml</code>, and it is possible to point elsewhere
+with the <code>--config</code> flag. For your first run, it should be sufficient to call the <code>site-builder</code>
+with <code>--config sites-config.yaml</code>, which is already configured appropriately.</p>
 <p>If, for any reason, you didn't add <code>walrus</code> to <code>$PATH</code>, make sure to configure a pointer to the
 binary, see below.</p>
 <h2 id="additional-options"><a class="header" href="#additional-options">Additional options</a></h2>

pr-preview/pr-148/usage/setup.html

@@ -269,7 +269,7 @@ <h2 id="installation"><a class="header" href="#installation">Installation</a></h
 </div>
 </div>
 <p>You can download the latest build from our Google Cloud Storage (GCS) bucket (correctly setting the
-<code>$SYSTEM</code> variable)`:</p>
+<code>$SYSTEM</code> variable):</p>
 <pre><code class="language-sh">SYSTEM= # set this to your system: ubuntu-x86_64, ubuntu-x86_64-generic, macos-x86_64, macos-arm64, windows-x86_64.exe
 curl https://storage.googleapis.com/mysten-walrus-binaries/walrus-testnet-latest-$SYSTEM -o walrus
 chmod +x walrus

pr-preview/pr-148/usage/web-api.html

@@ -287,7 +287,7 @@ <h2 id="http-api-usage"><a class="header" href="#http-api-usage">HTTP API Usage<
 </div>
 <div>
 <p>Walrus aggregators and publishers expose their API specifications at the path <code>/v1/api</code>. You can
-view this in the browser` e.g., at <a href="https://aggregator.walrus-testnet.walrus.space/v1/api">https://aggregator.walrus-testnet.walrus.space/v1/api</a></p>
+view this in the browser, e.g., at <a href="https://aggregator.walrus-testnet.walrus.space/v1/api">https://aggregator.walrus-testnet.walrus.space/v1/api</a></p>
 </div>
 </div>
 <h3 id="store"><a class="header" href="#store">Store</a></h3>

pr-preview/pr-148/walrus-sites/builder-config.html

@@ -191,9 +191,9 @@ <h1 id="configuring-the-site-builder"><a class="header" href="#configuring-the-s
 through sensible defaults, so you should not need to touch them. Yet, for completeness, we provide
 here the details for all the configuration options.</p>
 <h2 id="minimal-configuration"><a class="header" href="#minimal-configuration">Minimal configuration</a></h2>
-<p>The config file is expected to be in <code>./builder.yaml</code>, and it is possible to point elsewhere with
-the <code>--config</code> flag. For your first run, it should be sufficient to call the <code>site-builder</code> with
-<code>--config site-builder/assets/builder-example.yaml</code>, which is already configured appropriately.</p>
+<p>The config file is expected to be in <code>./sites-config.yaml</code>, and it is possible to point elsewhere
+with the <code>--config</code> flag. For your first run, it should be sufficient to call the <code>site-builder</code>
+with <code>--config sites-config.yaml</code>, which is already configured appropriately.</p>
 <p>If, for any reason, you didn't add <code>walrus</code> to <code>$PATH</code>, make sure to configure a pointer to the
 binary, see below.</p>
 <h2 id="additional-options"><a class="header" href="#additional-options">Additional options</a></h2>

pr-preview/pr-148/walrus-sites/tutorial-publish.html

@@ -276,6 +276,19 @@ <h2 id="update-the-site"><a class="header" href="#update-the-site">Update the si
 <div>
 <p>The wallet you are using must be the <em>owner</em> of the Walrus Site object to be able to update it.</p>
 </div>
+</div>
+<div id="admonition-extending-the-expiration-date-of-an-existing-site" class="admonition admonish-danger" role="note" aria-labelledby="admonition-extending-the-expiration-date-of-an-existing-site-title">
+<div class="admonition-title">
+<div id="admonition-extending-the-expiration-date-of-an-existing-site-title">
+<p>Extending the expiration date of an existing site</p>
+</div>
+<a class="admonition-anchor-link" href="#admonition-extending-the-expiration-date-of-an-existing-site"></a>
+</div>
+<div>
+<p>To extend the expiration date of a previously-stored site, use the <code>update</code> command with the
+<code>--force</code> flag, and specify the number of additional epochs (from the current epoch) with the
+<code>--epochs</code> flag.</p>
+</div>
 </div>
 
                     </main>