Create a reference to a new, unnamed cloud object:

Refer to a cloud object by its full URL:

Refer to a named cloud object with an absolute path:

Refer to a named cloud object with a relative path:

Refer to a named cloud object owned by a specific user:

Refer to a named object inside a base directory:

Refer to a named cloud object in a subdirectory of the user's directory in the cloud:

Use a URL to construct a CloudObject:

Add a persistent option to the CloudObject reference:

Create a public cloud object, specifying the permissions in the CloudObject expression:

The public permissions are in effect:

Add a persistent option with one setting to the CloudObject reference:

Nest the CloudObject inside another to change the permission setting:

Save a computed value in a cloud object:

Read an expression stored in a cloud object:

Remove the cloud object:

Create a reference that will be a directory and a reference to an "index.nb" object inside the directory:

Create the directory and deploy a notebook to the index location:

When visiting the directory URL, the contents of "index.nb" will be shown.

Relative paths are resolved with respect to CloudDirectory:

The cloud object is created under the "mydir" directory:

Cloud objects with an absolute path are created under $CloudRootDirectory:

A cloud object with an empty absolute path is the same as $CloudRootDirectory:

A cloud object can be constructed from a simple file name and a directory object with CloudObject or with FileNameJoin:

LocalObject is used for local persistent storage:

Applying CloudObject itself does not create an actual object in the cloud; it only refers to an object. So accessing the URL immediately will return a Not Found page:

Only by writing content to the cloud object is it actually created in the cloud:

Relative paths are related to the current CloudDirectory[], so if SetCloudDirectory is used, care should be taken to restore it after use if relative paths are used everywhere.

Refer to an object in the home directory:

Change to a different working directory:

Now the same reference from above produces a different URL:

The original object can be referred to with an absolute path instead, which does not depend on CloudDirectory[]:

The original object can also be constructed with a relative path and a base directory, specified either with a path or a cloud object:

Reset the cloud directory to its default:

Now the original relative reference works as it did:

The empty string is treated as an empty relative path and will resolve to the same as CloudDirectory[]. Change the current cloud directory:

Compare a cloud object with an empty relative path to the current cloud directory:

Change the current cloud directory back to its default: