Skip to content

Commit

Permalink
Stick multi-export/S3 docs in dropdown accordion
Browse files Browse the repository at this point in the history
  • Loading branch information
jhiemstrawisc committed Apr 16, 2024
1 parent ab10884 commit 407b47c
Showing 1 changed file with 4 additions and 1 deletion.
5 changes: 4 additions & 1 deletion docs/pages/serving_an_origin.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -162,6 +162,7 @@ If no `Origin.Exports` block is provided to Pelican, these values will also be a
> **NOTE:** Pelican tries to resolve differences between origin and namespace configurations by respecting the more restrictive of the two. If you serve an origin that enables public reads, but the underlying prefix it exports disables all reads, you won't be able to read from that namespace.
### Multi-Export Origins
<details><summary>Click to see more...</summary>

The previous examples have shown how one might export a single namespace, but Pelican origins can export multiple paths from the same storage backend under different namespaces. For example, assume you have have two posix directories called `/my/data/public` and `/my/data/private`. If you want to make your public data available under the namespace `/my/prefix/public` and your private data available under `/my/prefix/private`, you'll need to configure a multi-export origin, which is accomplished through the origin's `Exports` block. Below is an example of what that looks like, along with how you could configure access control for the two namespaces:

Expand All @@ -185,6 +186,7 @@ Origin:
```

> **NOTE:** While multiple namespaces can be exported by the same origin, they must all have the same underlying storage type. That is, if the origin serves files from POSIX, it must only serve files from POSIX and not S3.
</details>
### Additional Command Line Arguments for Origins

Expand All @@ -202,6 +204,7 @@ This section documents additional arguments you can pass via the command line wh
For more information about available yaml configuration options, refer to the [Parameters page](./parameters.mdx).

## Launch the Origin With an S3 Storage Backend
<details><summary>Click to see more...</summary>

### What is S3?

Expand Down Expand Up @@ -296,7 +299,7 @@ Origin:
```

In this configuration, users who wish to fetch objects from the origin will still need to know the name of the bucket that hosts those objects. For example, the AWS public bucket `noaa-wod-pds` has an object called `MD5SUMS`, and with this configuration the object can be fetched at `/aws-public/noaa-wod-pds/MD5SUMS`.

</details>

## Login to Admin Website

Expand Down

0 comments on commit 407b47c

Please sign in to comment.