v0.4.0

This version introduces:

• The latch ls subcommand ~ list the contents of LatchData root or any directory.
• Login and authentication now uses a persistent token. latch login will only need to be run once.

Note that latch login will need to be run again manually after downloading this version.

The latch ls subcommand

Introducing the latch ls subcommand. Use it to "list" the contents of any directory on the platform.

Usage: latch ls [OPTIONS] [REMOTE_DIRECTORIES]...

  List remote files in the command line. Supports multiple directory
  arguments.

  Visit docs.latch.bio to learn more.

Using the subcommand with no arguments will list the contents of your managed root directory.

$ latch ls
Name:                                                           Type:                      Size:         Last Modified:
20A_retests                                                  directory                  -             -
Amplification Project                                    directory                  -             -
Prime_Editing                                               directory                  -             -

Directories can be specified as:

• absolute paths ~ /my/directory
• latch protocol URLs ~ latch:///my/directory
• names within the root of the filesystem ~ my-directory

Persistent Token

The CLI now uses a persistent token with no expiration to authenticate users. This means that users only have to login once. This also means that users of a machine without access to a browser can manually copy their token to ~/.latch/token

The token is still stored at ~/.latch/token and can be found https://console.latch.bio/settings/developer. It is critical that the user engage in best practices when storing this value, eg. avoiding commiting it in VCS or sending it to others via email, slack.