cloud filesystem -- video links and better explanations

Author: williamstein

src/packages/frontend/compute/cloud-filesystem/cloud-filesystems.tsx

@@ -148,19 +148,40 @@ export default function CloudFilesystems({ project_id }: Props) {
 
   return (
     <div>
-      <Button style={{ float: "right" }} onClick={refresh}>
+      <Button style={{ position: "absolute", right: 0 }} onClick={refresh}>
         <Icon name="refresh" />
         Refresh{" "}
         {refreshing ? <Spin style={{ marginLeft: "15px" }} /> : undefined}
       </Button>
       <h2 style={{ textAlign: "center" }}>Cloud Filesystems</h2>
-      <p style={{ maxWidth: "700px", margin: "15px auto" }}>
+      <div style={{ textAlign: "center" }}>
+        <Button
+          href="https://youtu.be/zYoldE2yS3I"
+          target="_new"
+          style={{ marginRight: "15px" }}
+        >
+          <Icon name="youtube" style={{ color: "red" }} />
+          Short Demo
+        </Button>
+        <Button href="https://youtu.be/uk5eA5piQEo" target="_new">
+          <Icon name="youtube" style={{ color: "red" }} />
+          Longer Demo
+        </Button>
+      </div>
+      <p
+        style={{
+          maxWidth: "700px",
+          margin: "15px auto",
+          fontSize: "11pt",
+          color: "#666",
+        }}
+      >
         CoCalc Cloud Filesystems are scalable distributed POSIX shared
-        filesystems with fast local caching. They are mounted and usable
-        simultaneously from all compute servers in a project. There are no
-        limits on how much data you can store. You do not specify the size of a
-        cloud filesystem in advance. The cost per GB is typically much less than
-        a compute server disk, but you pay for how many operations you do.
+        filesystems with fast local caching. Use them simultaneously from all
+        compute servers in this project. There are no limits on how much data
+        you can store. You do not specify the size of a cloud filesystem in
+        advance. The cost per GB is typically much less than a compute server
+        disk, but you pay network usage and operations.
       </p>
 
       <div style={{ margin: "5px 0" }}>

src/packages/frontend/compute/cloud-filesystem/help.tsx

@@ -1,4 +1,5 @@
 import { Modal } from "antd";
+import { A } from "@cocalc/frontend/components";
 
 export function HelpModal({ open, setOpen }) {
   return (
@@ -17,44 +18,64 @@ export function HelpText() {
   return (
     <div>
       <h2>Filesystem Commands</h2>
-      Type <code>cocalc fs -h</code> in a terminal running on a compute server
-      to see the options for the filesystem cocalc subcommand. This command has
-      several helpful subcommands for working with Cloud Filesystems, including
-      the following:
+      <p>
+        Type <code>cocalc -h</code> in a terminal running on a compute server to
+        see the options for working with Cloud Filesystems. In most cases you
+        should run the <code>cocalc</code> command in a terminal from in a
+        directory in the cloud filesystem (similar to how git is aware of the
+        repo you are in).
+      </p>
+      <p>
+        The <code>cocalc warmup</code> command is especially important to know
+        about.
+      </p>
       <ul style={{ marginTop: "15px" }}>
         <li>
           <strong>
-            <code>cocalc fs stats &lt;path&gt;</code>:
+            <code>cocalc warmup </code>:
           </strong>{" "}
-          Show realtime performance statistics of a Cloud Filesystem. In
-          particular, you can see what objects are being uploaded or downloaded
-          to better understand network usage, and whether any data is not yet
-          uploaded before turning off a compute server.
+          Downloads chunks for the current working directory to the local disk
+          cache for much faster subsequent access. The disk cache (which is in
+          <code>/data/.cloud-filesystem/cache/</code>) uses up to 90% of your
+          disk and survives reboots but not deprovisioning. You may get much
+          better performance with a Cloud Filesystem by enlarging a compute
+          server's disk (which is easy to do at any time), since then more of it
+          can be used for cache.
         </li>
-
         <li>
           <strong>
-            <code>cocalc fs sync &lt;source&gt; &lt;dest&gt;</code>:
+            <code>cocalc backup</code>:{" "}
+          </strong>
+          Create and manage incremental backups. Run this command with no
+          arguments from within the cloud filesystem to make a backup that is
+          stored inside of the cloud filesystem itself. You can also make
+          backups to other cloud filesystems or directories.
+        </li>
+        <li>
+          <strong>
+            <code>cocalc sync &lt;source&gt; &lt;dest&gt;</code>:
           </strong>{" "}
           Efficiently sync files from a source directory to a dest directory.
           This is similar to rsync but potentially much faster since it is aware
-          of how Cloud Filesystem stores data. It's also an efficient way to get
+          of how Cloud Filesystems store data. It's also an efficient way to get
           data into and out of your Cloud Filesystem.
         </li>
-
         <li>
           <strong>
-            <code>cocalc fs warmup &lt;path&gt;</code>:
+            <code>cocalc cloudfs stat</code>:
           </strong>{" "}
-          Downloads all the chunks for the given path to the local disk cache
-          for much faster subsequent access. The disk cache (which is in
-          <code>/data/.cloud-filesystem/cache/</code>) uses up to 90% of your
-          disk and survives reboots but not deprovisioning. You may get much
-          better performance with a Cloud Filesystem by enlarging your compute
-          servers main disk (which is easy to do at any time), since then more
-          of it can be used for cache.
+          Show realtime performance statistics of a Cloud Filesystem. In
+          particular, you can see what objects are being uploaded or downloaded
+          to better understand network usage, and whether any data is not yet
+          uploaded before turning off a compute server.
         </li>
       </ul>
+      Cloud Filesystems use <A href="https://juicefs.com/en/">JuiceFS</A> under
+      the hood, and there is also a{" "}
+      <A href="https://juicefs.com/docs/community/command_reference">
+        juicefs command
+      </A>{" "}
+      that you can explore.
     </div>
   );
 }

src/packages/frontend/frame-editors/crm-editor/tables/cloud-filesystems.ts

@@ -13,6 +13,7 @@ register({
         id: null,
         project_id: null,
         account_id: null,
+        bytes_used: null,
         bucket: null,
         bucket_storage_class: null,
         bucket_location: null,
@@ -31,6 +32,7 @@ register({
         deleting: null,
         mount_options: null,
         keydb_options: null,
+        purchase_id: null,
       },
     ],
   },